Skip to content

feat(cluster-shield): add logic to load OpenShift ca cert to cluster shield #2117

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

maratsal
Copy link
Contributor

add logic to load OpenShift ca cert to be able to use it when communicate to internal registry without using registry_ssl.verify=false to avoid error like below:

failed to load image with remote analyzer: Get "https://image-registry.openshift-image-registry.svc:5000/v2/": tls: failed to verify certificate: x509: certificate signed by unknown authority

What this PR does / why we need it:

Checklist

  • Title of the PR starts with type and scope, (e.g. feat(agent,node-analyzer,sysdig-deploy):)
  • Chart Version bumped for the respective charts
  • Variables are documented in the README.md (or README.tpl in some charts)
  • Check GithubAction checks (like lint) to avoid merge-check stoppers
  • All test files are added in the tests folder of their respective chart and have a "_test" suffix

…cate to internal registry without using registry_ssl.verify=false
@maratsal maratsal requested a review from a team as a code owner January 17, 2025 19:26
Copy link
Contributor

This PR is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale The issue or pull request is inactive and will be closed soon label Mar 19, 2025
@mavimo mavimo removed the stale The issue or pull request is inactive and will be closed soon label Mar 19, 2025
@francesco-furlan
Copy link
Contributor

@maratsal we plan to integrate this in the next Cluster Shield release (1.10.0)
cc: @AlbertoBarba

Copy link
Contributor

This PR is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale The issue or pull request is inactive and will be closed soon label May 21, 2025
Copy link
Contributor

This PR has been closed due to inactivity.

@github-actions github-actions bot closed this May 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge stale The issue or pull request is inactive and will be closed soon
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants