Support Need for ppc64le arch about tang-operator HOT 7 CLOSED

As tang-operator was integrated in OCP, if you wish to generate an alternative for it you might generate it with different name, to avoid collision with the one existing in OCP.

Can you please share your modifications to try to reproduce it?

from tang-operator.

Hi @sarroutbi ,

I have updated change related to architect in Dockerfile which can be use for the operator image.

-RUN CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build -a -o manager main.go
+RUN CGO_ENABLED=0 GOOS=linux GOARCH=ppc64le go build -a -o manager main.go

and as per description it is not related to naming of operator it is more looking like issue related to install plan which is not available for particular subscription.

can you please look into it?

from tang-operator.

Hi @sarroutbi ,

Tang operator is working fine after i have followed your blogpost :
https://cloud.redhat.com/blog/tang-operator-providing-nbde-in-openshift#:~:text=You%20can%20deploy%20a%20tang,provides%20to%20achieve%20this%20automation.

But it only seems the problem for the clevis steps i am not able to run clevis machine after rebooting.

from tang-operator.

If tang-operator is up and running, you can just check if it can encrypt / decrypt messages for a machine with access to it:

echo "top secret" | clevis encrypt tang '{"url":"http://your-tang-operator-url.test"}' > test.jwe
clevis decrypt tang '{"url":"http://your-tang-operator-url.test.com/"}' < test.jwe

If after the second message you get "top secret", then it is working fine

from tang-operator.

i have tried above command to test whether tang operator is working :

i can see below result:

The advertisement contains the following signing keys:

aGBhcy1jOPH_utAclZKzfmF65IM

Do you wish to trust these keys? [ynYN] y
# clevis decrypt tang '{"url":"<<URL>>"}' < test.jwe
top secret

is it fine?

from tang-operator.

Yes, that is fine. It seems correctly configured.

from tang-operator.

For cross compilation, you can generate build for a different architecture by specifying appropriate GOARCH on make "docker-build":

Examples:
GOARCH=ppc64le make docker-build docker-push IMG="quay.io/sarroutb/testimage:v0.0.1"
GOARCH=s390x make docker-build docker-push IMG="quay.io/sarroutb/testimage:v0.0.1"

If no information is provided in GOARCH, amd64 (the current one) will be used

from tang-operator.