cmd/k8s-operator: Move login server value to top-level (#16470)

This commit modifies the operator helm chart values to bring the newly
added `loginServer` field to the top level. We felt as though it was a bit
confusing to be at the `operatorConfig` level as this value modifies the
behaviour or the operator, api server & all resources that the operator
manages.

Updates https://github.com/tailscale/corp/issues/29847

Signed-off-by: David Bond <davidsbond93@gmail.com>

cmd/k8s-operator/deploy/chart/templates/deployment.yaml

@@ -69,7 +69,7 @@ spec:
                 fieldRef:
                   fieldPath: metadata.namespace
             - name: OPERATOR_LOGIN_SERVER
-              value: {{ .Values.operatorConfig.loginServer }}
+              value: {{ .Values.loginServer }}
             - name: CLIENT_ID_FILE
               value: /oauth/client_id
             - name: CLIENT_SECRET_FILE

cmd/k8s-operator/deploy/chart/values.yaml

@@ -9,6 +9,9 @@ oauth: {}
   # clientId: ""
   # clientSecret: ""
 
+# URL of the control plane to be used by all resources managed by the operator.
+loginServer: ""
+
 # Secret volume.
 # If set it defines the volume the oauth secrets will be mounted from.
 # The volume needs to contain two files named `client_id` and `client_secret`.
@@ -72,9 +75,6 @@ operatorConfig:
   # - name: EXTRA_VAR2
   #   value: "value2"
 
-  # URL of the control plane to be used by all resources managed by the operator.
-  loginServer: ""
-
 # In the case that you already have a tailscale ingressclass in your cluster (or vcluster), you can disable the creation here
 ingressClass:
   enabled: true