Open mneverov opened 9 months ago
Let me work for it and will base k8s.io/component-base/cli
to refactor the code for use structured parameters.
/assign
@mneverov I may have misunderstood the meaning here. You just want the three variables to support environment variable passing, right?
@liangyuanpeng yes, that's correct.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
@liangyuanpeng are you still working on this? I would like to take over if you abandoned this ticket.
/remove-lifecycle rotten
/assign
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Currently, there is only few config params -
kubeconfig
,apiserver
,health-probe-address
that are passed to the operator as command line arguments. It should be possible to configure the operator with arguments and environment variables.