smartkuk
commented
1 year ago Additionally, if I use the helm command to install the chart in the same repository, the status looks correct. Some information has been covered with garbage information.
The storage under the harbor name is the same storage used above.
$ helm repo list
NAME URL
prometheus-community https://prometheus-community.github.io/helm-charts
stable https://charts.helm.sh/stable
ingress-nginx https://kubernetes.github.io/ingress-nginx
harbor https://xxxxxxxxxx:0000/chartrepo/bxcp-system-common
argo https://argoproj.github.io/argo-helm
member-harbor https://yyyyyyyyyy:0000/chartrepo/bxcp-system-common
$ helm install taiga-1026 harbor/tomcat
NAME: taiga-1026
LAST DEPLOYED: Fri Jun 16 09:50:14 2023
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
CHART NAME: tomcat
CHART VERSION: 10.9.2
APP VERSION: 10.1.9
** Please be patient while the chart is being deployed **
1. Get the Tomcat URL by running:
NOTE: It may take a few minutes for the LoadBalancer IP to be available.
Watch the status with: 'kubectl get svc --namespace default -w taiga-1026-tomcat'
export SERVICE_IP=$(kubectl get svc --namespace default taiga-1026-tomcat --template "{{ range (index .status.loadBalancer.ingress 0) }}{{ . }}{{ end }}")
echo "Tomcat URL: http://$SERVICE_IP/"
echo "Tomcat Management URL: http://$SERVICE_IP/manager"
2. Login with the following credentials
echo Username: user
echo Password: $(kubectl get secret --namespace default taiga-1026-tomcat -o jsonpath="{.data.tomcat-password}" | base64 -d)
$ helm history taiga-1026
REVISION UPDATED STATUS CHART APP VERSION DESCRIPTION
1 Fri Jun 16 09:50:14 2023 deployed tomcat-10.9.2 10.1.9 Install complete
hiddeco
Used Google translate
hi I am currently using the flux v1 version and want to change to the v2 version, so I am researching it. While trying to install and deploy to a kind cluster in my local WSL Ubuntu environment, a strange phenomenon occurred, so I made an inquiry here.
The status of the tomcat Pod resource created through the HelmRelease resource is normal, but why does the status of the HelmRelease resource become an error after waiting for about 5 minutes? I googled a lot and followed all the steps related to "retries exhausted". But nothing worked. Shouldn't the contents that are uploaded from Get Started or Installation that you guys have made work at least to build trust in the component?
Below is kind cluster configuration.
Below is the client version I am using.
I registered the Helm chart and wanted to distribute the chart, so I set it up as follows.
And the nginx chart was installed with the HelmRepository setting completed normally.
After waiting for about 5 minutes, the nginx-testing-1 HelmRelease resource was found in the following state. The problem is that the Pod resource status is normal, but I don't know why the HelmRelease resource is abnormal.
The following is the result of checking the status with the kubectl command. Some information has been covered with garbage information.
Here is the helm controller log:
Below is the tomcat pod log. You might be confused because nginx is included in the name, but it is tomcat.