che: Can't use custom registries
Describe the bug
I have a problem trying to use custom devfile and custom plugin registry. I can build and deploy them without any errors or problems, but the changes I made don’t show up. Neither the custom Stack from the devfile registry nor the added plugin of the plugin registry. To build the registries I use the build.sh, which is contained in the registries repos. To deploy I use:
NAMESPACE="kube-che"
DOMAIN="$(minikube ip).nip.io"
helm upgrade --install che-plugin-registry \
--debug \
--namespace ${NAMESPACE} \
--set global.ingressDomain=${DOMAIN} \
./kubernetes/che-plugin-registry/
for the plugin registry and:
NAMESPACE="kube-che"
DOMAIN="$(minikube ip).nip.io"
helm upgrade --install che-devfile-registry \
--debug \
--namespace ${NAMESPACE} \
--set global.ingressDomain=${DOMAIN} \
./deploy/kubernetes/che-devfile-registry/
for the devfile registry.
Che version
- latest
- nightly
- other: 7.4.0
Steps to reproduce
Expected behavior
Runtime
- kubernetes (include output of
kubectl version)
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.4", GitCommit:"67d2fcf276fcd9cf743ad4be9a9ef5828adc082f", GitTreeState:"clean", BuildDate:"2019-09-18T14:51:13Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.4", GitCommit:"67d2fcf276fcd9cf743ad4be9a9ef5828adc082f", GitTreeState:"clean", BuildDate:"2019-09-18T14:41:55Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
- Openshift (include output of
oc version) - minikube (include output of
minikube versionandkubectl version) - minishift (include output of
minishift versionandoc version) - docker-desktop + K8S (include output of
docker versionandkubectl version) - other: (please specify)
Screenshots
Installation method
- chectl command: chectl server:start -p minikube
- che-operator
- minishift-addon
- I don’t know
Environment
- my computer
- Windows
- Linux
- macOS
- Cloud
- Amazon
- Azure
- GCE
- other (please specify)
- other: please specify
Additional context
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 15 (8 by maintainers)
I have solved it. I had to specify a custom tag while executing build.sh and specify that custom tag while deploying. Unfortunately I have another problem now, when trying to start a workspace, but since it is not a problem about building/deploying I’ll open a new isuue for that.
When I opened this issue it was, in my oppinion, more a bug than a question, but at the moment i think it is indeed more a question than a bug.