SysDig agent fails to install on recently created IBM Cloud cluster #110
Comments
seansund
changed the title
- Replaces check for specific `default-icr-io` name with a pattern match Addresses draios#110
- Replaces check for specific `default-icr-io` name with a pattern match Addresses draios#110
|
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 |
|
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 |
|
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? |
|
@powellquiring Didn't realize that there's already a PR open for it #111 |
|
@seansund Thanks for fixing this! It was merged, can you please close this issue? |
|
Does the fix need to be deployed into production? |
|
@powellquiring It was deployed to IBM BIZ https://ibm.biz/install-sysdig-k8s-agent |
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-iopull 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 namedall-icr-iois created in the cluster.Unfortunately it looks like the script looks for a particular secret with the name
default-icr-ioinstead of doing some kind of pattern matching.The text was updated successfully, but these errors were encountered: