Skip to content
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

SysDig agent fails to install on recently created IBM Cloud cluster #110

Open
seansund opened this issue Apr 22, 2020 · 7 comments
Open

Comments

@seansund
Copy link
Contributor

I created a new RedHat OpenShift cluster on IBM Cloud yesterday and attempted to install the Sysdig agent. The script failed because it couldn't find the default-icr-io pull secret for the IBM Container Registry.

It looks like some time over the weekend the strategy for naming pull secrets for the Container Registry changed. Previously, multiple pull secrets were created for each region with the prefix of default. Now a single pull secret named all-icr-io is created in the cluster.

Unfortunately it looks like the script looks for a particular secret with the name default-icr-io instead of doing some kind of pattern matching.

@seansund seansund changed the title SysDig agent fails to install on "new" IBM Cloud cluster SysDig agent fails to install on recently created IBM Cloud cluster Apr 22, 2020
seansund added a commit to seansund/sysdig-cloud-scripts that referenced this issue Apr 22, 2020
- Replaces check for specific `default-icr-io` name with a pattern match

Addresses draios#110
seansund added a commit to seansund/sysdig-cloud-scripts that referenced this issue Apr 22, 2020
- Replaces check for specific `default-icr-io` name with a pattern match

Addresses draios#110
@powellquiring
Copy link

I just ran into this issue as well. Is there a way to up the priority on this? https://ibm-cloudplatform.slack.com/archives/GDGB25SP6/p1588006017117600

@PatrickDuncan
Copy link
Contributor

PatrickDuncan commented Apr 27, 2020

Hey, we'll look into changing this soon. Not sure about the pattern matching, that seems a bit volatile. It could pick a secret without the necessary permissions or the pattern could change.

Thanks for opening a ticket

@powellquiring
Copy link

There is going to be live, on-line classes at the Think conference that use this. @PatrickDuncan can this be fixed tomorrow? Do you need help?

@PatrickDuncan
Copy link
Contributor

PatrickDuncan commented Apr 29, 2020

@powellquiring Didn't realize that there's already a PR open for it #111

@PatrickDuncan
Copy link
Contributor

@seansund Thanks for fixing this! It was merged, can you please close this issue?

@powellquiring
Copy link

Does the fix need to be deployed into production?

@PatrickDuncan
Copy link
Contributor

@powellquiring It was deployed to IBM BIZ https://ibm.biz/install-sysdig-k8s-agent

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

No branches or pull requests

3 participants