This message was deleted.
# general
a
This message was deleted.
s
Hi TaeilSeok, I have the same issue with Rancher v2.5.5. (it is running under Kubernetes v.1.19.7 HA Cluster ). When I enabled charts in catalog, this errors occurred: "Error in HTTP GET to [https://apphub.aliyuncs.com/index.yaml], error: Get "https://apphub.aliyuncs.com/index.yaml": dial tcp: lookup apphub.aliyuncs.com on 169.254.25.1053 server misbehaving" After it has been gone in page refresh. -- And two built kubernetes.io charts doesn't work limited access. After refreshed: Unexpected HTTP status code 403 from [https://kubernetes-charts-incubator.storage.googleapis.com/index.yaml], expected 200 https://kubernetes-charts.storage.googleapis.com/index.yaml This XML file does not appear to have any style information associated with it. The document tree is shown below. <Error> <Code>AccessDenied</Code> <Message>Access denied.</Message> <Details>Anonymous caller does not have storage.objects.get access to the Google Cloud Storage object.</Details> </Error> ---
Hi TaeilSeok, I have the same issue with Rancher v2.5.5. (it is running under Kubernetes v.1.19.7 HA Cluster ). When I enabled charts in catalog, this errors occurred: "Error in HTTP GET to [https://apphub.aliyuncs.com/index.yaml], error: Get "https://apphub.aliyuncs.com/index.yaml": dial tcp: lookup apphub.aliyuncs.com on 169.254.25.1053 server misbehaving" After it has been gone in page refresh. -- And two built kubernetes.io charts doesn't work limited access. After refreshed: Unexpected HTTP status code 403 from [https://kubernetes-charts-incubator.storage.googleapis.com/index.yaml], expected 200 https://kubernetes-charts.storage.googleapis.com/index.yaml This XML file does not appear to have any style information associated with it. The document tree is shown below. <Error> <Code>AccessDenied</Code> <Message>Access denied.</Message> <Details>Anonymous caller does not have storage.objects.get access to the Google Cloud Storage object.</Details> </Error> ---
For Information updates: I've deployed Rancher 2.5.6-rc4 on my k8s cluster with internal nginx-ingress LB connected, and I've added Bitnami charts catalog. Charts creation and updating/syncing process has been finished successfully. See on my attached screen. All other issues has been gone (for ex. pod/helm-operation failed)