You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.
commit 6bc51317caaf7f80a6c27a9624e6701b89c67dc9
Author: Alfonso Acosta <fons@syntacticsugar.consulting>
Date: Mon Jan 13 19:02:28 2020 +0100
Honor KUBECONFIG env variable
Also, delegate the creation of incluster configuration
to the Kubernetes library.
As a result, we are not making use of the `--in-cluster`
argument anymore. Both the `--in-cluster` and `--kube-config`
arguments have been deprecated (you can use the `KUBECONFIG`
env variable instead).
I guess the doc you had in mind is docs/contributing/get-started-developing.md that still references --k8s-in-cluster as a way to tell flux daemon whether it runs in Kubernetes or not. Looks like one is supposed to set KUBECONFIG variable now.
At this time, I believe it is understood that nobody out there should be getting started with Flux v1 development anymore.
I'm going to close this without action, but we hope you've been able to upgrade to Flux v2 and note that Flux v1 remains in maintenance mode. Bugs with Flux v1 can be addressed as long as we keep it in maintenance mode, according to #3320 and the plan laid out in the Flux Migration Timetable. 👍
The documentation no longer works and the flag
k8s-in-cluster
is no longer used?What's the best/correct way to do local development against a remote cluster?
The text was updated successfully, but these errors were encountered: