draios / draios/sysdig-cloud-scripts
SysDig agent fails to install on recently created IBM Cloud cluster
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 83
- Forks
- 105
- Avg merge
- 3h 53m
- Merged PRs (30d)
- 1
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the installation script that searches for the default-icr-io pull secret and reproduce the failure on a recently created IBM Cloud RedHat OpenShift cluster. Compare the cluster's available pull-secret names with the lookup behavior; done means the agent installs successfully when the cluster provides all-icr-io.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100