SECURESIGN-589 | Fulcio OIDC issuers configuration does not show in Web Form

[JasonPowr]

This pr fixes the issue laid out in this jira https://issues.redhat.com/browse/SECURESIGN-589, The main issues was with how the issuer info was stored in the api.

[JasonPowr]

/test tas-operator-e2e

[JasonPowr]

/test tas-operator-e2e

[cooktheryan]

/retest

[JasonPowr]

Dont merge this yet, I believe its only passing openshift e2e because I added this line:

secure-sign-operator/ci/openshift/sign-test.sh

Line 74 in ba7585b

oc logs -n openshift-rhtas-operator deployment/rhtas-operator-controller-manager

to the end of the test script

[JasonPowr]

This error is showing up in e2e on openshift

E0312 10:44:15.878404 1 reflector.go:147] pkg/mod/k8s.io/client-go@v0.28.5/tools/cache/reflector.go:229: Failed to watch *v1alpha1.Securesign: failed to list *v1alpha1.Securesign: json: cannot unmarshal array into Go struct field FulcioConfig.items.spec.fulcio.config.OIDCIssuers of type map[string]v1alpha1.OIDCIssuer
W0312 10:44:17.647975 1 reflector.go:535] pkg/mod/k8s.io/client-go@v0.28.5/tools/cache/reflector.go:229: failed to list *v1alpha1.Securesign: json: cannot unmarshal array into Go struct field FulcioConfig.items.spec.fulcio.config.OIDCIssuers of type map[string]v1alpha1.OIDCIssuer

[JasonPowr]

I believe the ci in openshift is failing because its building and deploying an fbc image, and in the fbc image its using an older version of the operator that wont have the necessary changes to the api to support this new fulcio config. Looking at the ci run its using the image: quay.io/redhat-user-workloads/rhtas-tenant/operator/rhtas-operator@sha256:e550dad4a7299118fe220cd4c145c6e2deee75d2e28e41525f9dc2fb6c9f7508
reference: if its still up: https://console-openshift-console.apps.build04.34d2.p2.openshiftapps.com/k8s/ns/ci-op-8n70cb7l/pods/tas-operator-e2e-install/logs

So we kinda have a chicken and egg thing here...
@osmman @bouskaJ @cooktheryan, whats the best way to proceed with this?

[JasonPowr]

I believe the ci in openshift is failing because its building and deploying an fbc image, and in the fbc image its using an older version of the operator that wont have the necessary changes to the api to support this new fulcio config. Looking at the ci run its using the image: quay.io/redhat-user-workloads/rhtas-tenant/operator/rhtas-operator@sha256:e550dad4a7299118fe220cd4c145c6e2deee75d2e28e41525f9dc2fb6c9f7508 reference: if its still up: https://console-openshift-console.apps.build04.34d2.p2.openshiftapps.com/k8s/ns/ci-op-8n70cb7l/pods/tas-operator-e2e-install/logs

So we kinda have a chicken and egg thing here... @osmman @bouskaJ @cooktheryan, whats the best way to proceed with this?

I think the best option to deal with this is to merge this pr, get a new operator image from konflux, I can then update the bundle and fbc images accordingly. wdyt?

[lance]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JasonPowr, lance

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [JasonPowr,lance]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[JasonPowr]

/test tas-operator-e2e