CM-830: Add TrustManager API types for trust-manager operand

[openshift-app-platform-shift]

Summary

• Introduces the TrustManager CRD (trustmanagers.operator.openshift.io/v1alpha1) as specified in enhancement proposal EP-1914
• Adds cluster-scoped singleton resource for day-2 installation and configuration of the trust-manager operand
• Registers FeatureTrustManager feature gate (Alpha, default disabled) for TechPreview gating

Changes

New Files

• api/operator/v1alpha1/trustmanager_types.go — TrustManager, TrustManagerSpec, TrustManagerConfig, SecretTargetsConfig, DefaultCAPackageConfig, TrustManagerControllerConfig, TrustManagerStatus, and enum types
• api/operator/v1alpha1/trustmanager_types_test.go — CRD integration tests (status defaults, singleton, scope, immutability)
• api/operator/v1alpha1/tests/trustmanagers.operator.openshift.io/trustmanager.testsuite.yaml — YAML test suite with 28 onCreate and 7 onUpdate validation scenarios
• config/crd/bases/operator.openshift.io_trustmanagers.yaml — Generated CRD manifest

Modified Files

• api/operator/v1alpha1/features.go — Added FeatureTrustManager feature gate
• api/operator/v1alpha1/zz_generated.deepcopy.go — Auto-generated deepcopy methods
• Generated client/lister/informer/applyconfigurations for TrustManager type

Key API Fields

• trustManagerConfig.logLevel (1-5), logFormat (text/json)
• trustManagerConfig.trustNamespace (immutable, default: cert-manager)
• trustManagerConfig.secretTargets (Disabled/Custom with authorizedSecrets)
• trustManagerConfig.filterExpiredCertificates (Enabled/Disabled)
• trustManagerConfig.defaultCAPackage (Enabled/Disabled)
• trustManagerConfig.resources, affinity, tolerations, nodeSelector
• controllerConfig.labels, controllerConfig.annotations

Test plan

• go build ./api/... compiles successfully
• make generate && make manifests runs without errors
• Go integration tests pass (go test ./api/operator/v1alpha1/... -run TestTrustManager)
• YAML test suite validated with envtest runner

🤖 Generated with Claude Code

[openshift-ci-robot]

@openshift-app-platform-shift[bot]: This pull request references CM-830 which is a valid jira issue.

Details

In response to this:

Summary

• Introduces the TrustManager CRD (trustmanagers.operator.openshift.io/v1alpha1) as specified in enhancement proposal EP-1914
• Adds cluster-scoped singleton resource for day-2 installation and configuration of the trust-manager operand
• Registers FeatureTrustManager feature gate (Alpha, default disabled) for TechPreview gating

Changes

New Files

• api/operator/v1alpha1/trustmanager_types.go — TrustManager, TrustManagerSpec, TrustManagerConfig, SecretTargetsConfig, DefaultCAPackageConfig, TrustManagerControllerConfig, TrustManagerStatus, and enum types
• api/operator/v1alpha1/trustmanager_types_test.go — CRD integration tests (status defaults, singleton, scope, immutability)
• api/operator/v1alpha1/tests/trustmanagers.operator.openshift.io/trustmanager.testsuite.yaml — YAML test suite with 28 onCreate and 7 onUpdate validation scenarios
• config/crd/bases/operator.openshift.io_trustmanagers.yaml — Generated CRD manifest

Modified Files

• api/operator/v1alpha1/features.go — Added FeatureTrustManager feature gate
• api/operator/v1alpha1/zz_generated.deepcopy.go — Auto-generated deepcopy methods
• Generated client/lister/informer/applyconfigurations for TrustManager type

Key API Fields

• trustManagerConfig.logLevel (1-5), logFormat (text/json)
• trustManagerConfig.trustNamespace (immutable, default: cert-manager)
• trustManagerConfig.secretTargets (Disabled/Custom with authorizedSecrets)
• trustManagerConfig.filterExpiredCertificates (Enabled/Disabled)
• trustManagerConfig.defaultCAPackage (Enabled/Disabled)
• trustManagerConfig.resources, affinity, tolerations, nodeSelector
• controllerConfig.labels, controllerConfig.annotations

Test plan

• go build ./api/... compiles successfully
• make generate && make manifests runs without errors
• Go integration tests pass (go test ./api/operator/v1alpha1/... -run TestTrustManager)
• YAML test suite validated with envtest runner

🤖 Generated with Claude Code

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

Hi @openshift-app-platform-shift[bot]. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-app-platform-shift[bot]
Once this PR has been reviewed and has the lgtm label, please assign bharath-b-rh for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[swghosh]

/close
redundant and contained in #423

[openshift-ci]

@swghosh: Closed this PR.

Details

In response to this:

/close
redundant and contained in #423

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.