<p>I have one kubernetes operator (ex: <code>kubectl get oracle_ctrl</code>). Now I want to provide custom arguments for the kubectl command.
ex: <code>kubectl apply oracle_ctrl --auto-discover=true --name=vcn1</code></p>
<p>I can write one more controller to do the same job. But I don't want to write one more controller and make use of existing controller.</p>
<p>Is it possible to use operator-sdk to provide custom args to kubectl?</p>

Madhu Kiran Seelam
<p>No, this isn't possible.</p>
<p><a href="https://github.com/kubernetes/kubectl/issues/914" rel="nofollow noreferrer">kubernetes/kubectl#914</a> has a little bit further discussion of this, but its essential description is &quot;we should start the proposal and design process to eventually write something better than <code>kubectl create</code> to support it&quot;.  Your CRD can <a href="https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#additional-printer-columns" rel="nofollow noreferrer">define additional columns to be shown in <code>kubectl get</code></a> but this is really the only <code>kubectl</code>-related extension point.  You could potentially create a <a href="https://kubernetes.io/docs/tasks/extend-kubectl/kubectl-plugins/" rel="nofollow noreferrer">kubectl plugin</a> or another CLI tool that does what you need.</p>
<p>Rather than using the <code>kubectl</code> imperative tools, it's often a better practice to directly write YAML artifacts and commit them to source control.  You can parameterize these using tools like Helm or Kustomize.  If <code>kubectl apply -f</code> or <code>helm install</code> is your primary way of loading things into the cluster, then you don't need custom CLI options to make this work.</p>
