jx install error for registry tokens creation during install in IKS

Created on 17 Jul 2019  路  7Comments  路  Source: jenkins-x/jx

Summary

I am trying to install jenkins x on an existing IKS cluster

Steps to reproduce the behavior

run the command jx install --provider=iks and input the values requested by the process.

Expected behavior

jenkins x should get deployed on existing IKS cluster.

Actual behavior

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"

Jx version

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"
}

```

Jenkins type

  • [x] Classic Jenkins

Kubernetes cluster

Operating system / Environment


jx is run on debian 9.0

areIKS arejenkins kinbug lifecyclrotten prioritimportant-longterm

Most helpful comment

Hi, we are facing the same issue here

All 7 comments

Unfortunately, I am experiencing the same issue.

Hi, we are facing the same issue here

Just wondering if this might be a solution:

  • Change IKS Registry handling with updated endpoints
  • Replace Token creation with IAMApi key creation and inject it into jenkins-docker-cfg
  • IBMCloud is creating default api keys to read docker images in the private registries (under the 'default' namespace). I believe it would be great to clone these secrets into the newly created namespaces (the environments) and add them to the default service accounts.

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.

Was this page helpful?
0 / 5 - 0 ratings