I am trying to install jenkins x on an existing IKS cluster
run the command jx install --provider=iks and input the values requested by the process.
jenkins x should get deployed on existing IKS cluster.
I see an error message:
"code": "CRT0002E",
"message": "The creation of registry tokens is discontinued. For more information about how to use API keys to automate access to your namespaces, see: https://cloud.ibm.com/docs/services/Registry?topic=registry-registry_access",
"request-id": "f929a09df5f092faf5794d178da7f2ea"
}
error: configuring the docker registry: configure cloud provider docker registry: getting IKS registry configuration: Request failed with status code: 410, ServerErrorResponse: {
"code": "CRT0002E",
"message": "The creation of registry tokens is discontinued. For more information about how to use API keys to automate access to your namespaces, see: https://cloud.ibm.com/docs/services/Registry?topic=registry-registry_access",
"request-id": "f929a09df5f092faf5794d178da7f2ea"
The output of jx version is:
2.0.474
ERROR: error - Request failed with status code: 410, ServerErrorResponse: {
"code": "CRT0002E",
"message": "The creation of registry tokens is discontinued. For more information about how to use API keys to automate access to your namespaces, see: https://cloud.ibm.com/docs/services/Registry?topic=registry-registry_access",
"request-id": "ea2b3c8547325cbfa801536521eae00e"
}
error: configuring the docker registry: configure cloud provider docker registry: getting IKS registry configuration: Request failed with status code: 410, ServerErrorResponse: {
"code": "CRT0002E",
"message": "The creation of registry tokens is discontinued. For more information about how to use API keys to automate access to your namespaces, see: https://cloud.ibm.com/docs/services/Registry?topic=registry-registry_access",
"request-id": "ea2b3c8547325cbfa801536521eae00e"
}
```
jx is run on debian 9.0
Unfortunately, I am experiencing the same issue.
Hi, we are facing the same issue here
Just wondering if this might be a solution:
What do you think?
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close
@jenkins-x-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.
Most helpful comment
Hi, we are facing the same issue here