Skip to content
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.

Best Way to do Local Development? #3188

Closed
ekristen opened this issue Jul 10, 2020 · 2 comments
Closed

Best Way to do Local Development? #3188

ekristen opened this issue Jul 10, 2020 · 2 comments
Assignees
Labels
bug docs Issue or PR relates to documentation

Comments

@ekristen
Copy link

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?

@ekristen ekristen added blocked-needs-validation Issue is waiting to be validated before we can proceed bug labels Jul 10, 2020
@kingdonb
Copy link
Member

I found the reference you're looking for:

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.

@kingdonb kingdonb added docs Issue or PR relates to documentation and removed blocked-needs-validation Issue is waiting to be validated before we can proceed labels Feb 19, 2021
@kingdonb kingdonb self-assigned this Feb 19, 2021
@kingdonb
Copy link
Member

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. 👍

Thanks for using Flux.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug docs Issue or PR relates to documentation
Projects
None yet
Development

No branches or pull requests

2 participants