Comments (1)
@phuongvtn: The label(s) area/logging
cannot be applied, because the repository doesn't have them.
In response to this:
Hi,
I'm newbie on clusterAPI operator and facing error log that appear continuously on caaph (addon-helm)
I'm testing clusterAPI with Openstack Infra that can provision workload cluster and using helmchartproxy for deploying cni (calico and cilium) for target workload
But, I see caaph pod report error log continuously about get kubeconfig for clusterBelow are logs that I collected about my facing:
1 helmreleaseproxy_controller.go:121] "Preparing to patch HelmReleaseProxy with return error" controller="helmreleaseproxy" controllerGroup="addons.cluster.x-k8s.io" controllerKind="HelmReleaseProxy" HelmReleaseProxy="<namespace>/<name_of_helmreleaseproxy>" namespace="<namespace>" name="<name_of_helmreleaseproxy>" reconcileID="xxx-xxx-xxxx-xxx-xxx" helmReleaseProxy="<name_of_helmreleaseproxy>" reterr="failed to get kubeconfig for cluster: context \"default-context\" does not exist" 1 controller.go:329] "Reconciler error" err="failed to get kubeconfig for cluster: context \"default-context\" does not exist" controller="helmreleaseproxy" controllerGroup="addons.cluster.x-k8s.io" controllerKind="HelmReleaseProxy" HelmReleaseProxy="<namespace>/<name_of_helmreleaseproxy>" namespace="<namespace>" name="<namespace>/<name_of_helmreleaseproxy>" reconcileID="xxx" 1 helmreleaseproxy_controller.go:121] "Preparing to patch HelmReleaseProxy with return error" controller="helmreleaseproxy" controllerGroup="addons.cluster.x-k8s.io" controllerKind="HelmReleaseProxy" HelmReleaseProxy="<namespace>/<name_of_helmreleaseproxy>" namespace="<namespace>" name="<name_of_helmreleaseproxy>" reconcileID="xxx" helmReleaseProxy="<name_of_helmreleaseproxy>" reterr=null
These error logs have been appeared right after the first deployment of helmchartproxy on target workload cluster successfully. Seem they from result of func KubeconfigGetter.GetClusterKubeconfig but I not sure
Although I tested updating helm values via helmchartproxy of target workload cluster as well as check revision of helmreleaseproxy (with corresponding namespace) and configmap of target workload cluster, all still update successfully, I not sure how the above logs may affect helmchart 's lifecycle as well as values of cni on target workload cluster in future
Do I missing configure or we can ignore these logs at current? Thanks
Environment:
- Cluster API version: v1.6.0
- Cluster API Add-on Provider for Helm version: v0.1.1-alpha.1
- minikube/kind version: v1.6.0
- Kubernetes version: (use
kubectl version
): v1.28.4- OS (e.g. from
/etc/os-release
): Ubuntu 20.04.4/kind bug
/area logging
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 kubernetes/test-infra repository.
from cluster-api-addon-provider-helm.
Related Issues (20)
- Add controllers tests for real Reconcile loop running with setup-envtest
- Add e2e validation for PRs
- Release Beta API version HOT 5
- Remove unnecessary pointer types in `HelmOptions` type
- Add e2e tests to support coverage of Helm install, upgrade, and uninstall HOT 1
- CAAPH considers an image tag as number instead of string HOT 11
- HelmReleaseProxy can't be created when there is a HelmChartProxy with the same name in a different namespace HOT 1
- Make targets should error if `REGISTRY` is unset HOT 1
- Duplicate HelmReleaseProxy resources after move - potential race HOT 5
- CAPI v1.7.0-beta.0 has been released and is ready for testing HOT 1
- Helm status doesn't update when underlying cluster status changes
- Unable to change namespace HOT 1
- Need docs for "How to do a product release" HOT 2
- Dry Run option
- Add yaml CI validation for metadata.yml (and probably all yaml in the repo) HOT 1
- Flaky unit test: TestReconcileForCluster HOT 2
- Apply user-defined metadata (labels and annotations) when creating the release namespace
- Support for OpenShift as Management Cluster HOT 1
- Should use a recent version of setup-envtest
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cluster-api-addon-provider-helm.