Skip to content

feat(v2): Provider secret ca - #77

Open
sabre1041 wants to merge 1 commit into
redhat-cop:v2from
sabre1041:provider-secret-ca
Open

feat(v2): Provider secret ca#77
sabre1041 wants to merge 1 commit into
redhat-cop:v2from
sabre1041:provider-secret-ca

Conversation

@sabre1041

Copy link
Copy Markdown
Contributor

Description

Update the certificate field in the Provider secret (cacert -> ca.crt)

Type of Change

  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation changes
  • style: Formatting, missing semi colons, etc; no code change
  • refactor: Refactoring production code
  • test: Adding missing tests, refactoring tests; no production code change
  • chore: Updating configs, etc; no production code change

Signed-off-by: Andrew Block <andy.block@gmail.com>
@sabre1041
sabre1041 changed the base branch from main to v2 August 31, 2026 01:17
@sabre1041
sabre1041 deployed to external-ci August 31, 2026 01:17 — with GitHub Actions Active
@tech2734

tech2734 commented Aug 31, 2026

Copy link
Copy Markdown

This fails in my environment. The provider does not become ready. Even though the secret contains a key called ca.crt with the certificate as the value, the secret that shows alongside the provider has "no value" for the ca cert.
provider-not-ready
ca-cert-set
no-value

Going to update MTV and try again

@tech2734

tech2734 commented Aug 31, 2026

Copy link
Copy Markdown

The ca.crt change was in MTV 2.12 only. I recommend writing both values cacert and ca.crt to support older versions. I am on OpenShift 4.18 and 2.12 is not even an option for me to upgrade to

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants