New RunLLM response generated >>> Question Hi wave I am inst Flyte #runllm-flyte-trial

New RunLLM response generated: >>>*# Question* Hi...

ancient-wolf-19325

08/13/2024, 12:50 PM

New RunLLM response generated: >>>*# Question* Hi 👋, I am installing flyte suing flyte-core helm chart using terraform as IAC, and we use okta as user authenticator but there are some manual steps we do mentioned here (Edit the

flyte-admin-secrets

secret and add the

oidc_client_secret

) but is there a way to add this to helm chart by some way when we install flyte ? (instead of manual edits) # Answer Yes, you can automate the inclusion of the

oidc_client_secret

in the Helm chart by leveraging pre-created Kubernetes Secret objects and referencing them in your Helm values file. This approach eliminates the need for manual edits. 1. Create the Secret: First, create a Kubernetes Secret containing the

oidc_client_secret

and other sensitive information.

Copy code

apiVersion: v1
kind: Secret
metadata:
  name: flyte-binary-client-secrets-external-secret
  namespace: flyte
type: Opaque
stringData:
  oidc_client_secret: <OIDC_CLIENT_SECRET>

Apply this secret using `kubectl`:

Copy code

kubectl apply -f <path-to-your-secret-file>.yaml

2. Reference the Secret in Helm Values: In your

values.yaml

file for the Helm chart, reference the newly created secret.

Copy code

configuration:
  auth:
    clientSecretsExternalSecretRef: flyte-binary-client-secrets-external-secret

This setup ensures that the secret is automatically included during the Helm chart installation, avoiding manual edits. Would you like more details on any specific part of this process? Sources: - Add support for leveraging pre-created secrets in flyte-binary helm chart - Flyte Deployment Configuration Auth Setup Slack Link https://flyte-org.slack.com/archives/CP2HDHKE1/p1723553433.496269 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

lively-journalist-67175

08/13/2024, 1:01 PM

@ancient-wolf-19325 But it looks like you are talking about flyte-binary helm chart and i am using flyte-core helm chart

ancient-wolf-19325

08/13/2024, 1:01 PM

The

flyte-core

Helm chart provides more configuration options and examples compared to the

flyte-binary

chart. It is recommended for users who need more control over their Flyte deployment, especially in multi-cluster setups or when avoiding plain text secrets in configuration files. For deploying Flyte using the

flyte-core

Helm chart, you can follow these steps: 1. Add the Flyte Helm Repository:

Copy code

helm repo add flyteorg https://flyteorg.github.io/flyte

2. Install Flyte using the
flyte-core
Helm chart:

Copy code

helm install -n flyte --create-namespace flyte flyteorg/flyte-core

3. Configuration: Customize your deployment by creating a

values-override.yaml

file with your specific configurations. For example, to configure the sensor agent, you can add:

Copy code

configmap:
      enabled_plugins:
        tasks:
          task-plugins:
            enabled-plugins:
              - container
              - sidecar
              - k8s-array
              - agent-service
            default-for-task-types:
              container: container
              sidecar: sidecar
              container_array: k8s-array
              sensor: agent-service
            plugins:
              agent-service:
                supportedTaskTypes:
                  - sensor

4. Upgrade the Deployment:

Copy code

helm upgrade flyte flyteorg/flyte-core -n flyte --values values-override.yaml

For more details, refer to the Flyte sensor agent documentation. Would you like more detail on any specific part of the deployment process? Sources: - Flyte sensor agent documentation - Flyte-core Helm chart PR 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

lively-journalist-67175

08/13/2024, 1:05 PM

@ancient-wolf-19325 my question is related to flyte-core helm chart and manual steps we do mentioned here (Edit the

flyte-admin-secrets

secret and add the

oidc_client_secret

) but is there a way to add this to helm chart by some way when we install flyte ?

ancient-wolf-19325

08/13/2024, 1:05 PM

Yes, you can automate the addition of the

oidc_client_secret

to the

flyte-core

Helm chart by specifying it in your

values.yaml

file. This avoids the need for manual edits post-installation. 1. Create a Secret: First, create a Kubernetes secret containing your OIDC client secret.

Copy code

kubectl create secret generic flyte-oidc-secret --from-literal=oidc_client_secret=<YOUR_OIDC_CLIENT_SECRET> -n flyte

2. Reference the Secret in
values.yaml
: Update your

values.yaml

to reference this secret. Here’s an example configuration:

Copy code

secrets:
      adminOauthClientCredentials:
        enabled: true
        clientSecret: <YOUR_OIDC_CLIENT_SECRET>

3. Install or Upgrade Flyte: Use Helm to install or upgrade Flyte with the updated

values.yaml

Copy code

helm upgrade --install flyte flyteorg/flyte-core -n flyte --values values.yaml

This approach ensures that the

oidc_client_secret

is included during the Helm installation or upgrade process, eliminating the need for manual secret edits. Would you like more detailed steps or a specific example? Sources: - Flyte-core Helm Chart PR 👍 0 button 👎 1 button 💡 Hint: Mention @ancient-wolf-19325 in the thread for followups.

lively-journalist-67175

08/13/2024, 1:09 PM

@ancient-wolf-19325 can we add two clientsecret here ?

Copy code

secrets:
      adminOauthClientCredentials:
        enabled: true
        clientSecret: <YOUR_OIDC_CLIENT_SECRET>

ancient-wolf-19325

08/13/2024, 1:09 PM

No, the

adminOauthClientCredentials

section in the

values.yaml

file does not support multiple

clientSecret

entries directly. However, you can create multiple secrets and reference them separately in your configuration. Here’s how you can manage multiple client secrets: 1. Create Multiple Secrets: Create separate Kubernetes secrets for each client secret.

Copy code

kubectl create secret generic flyte-oidc-secret --from-literal=oidc_client_secret=<YOUR_OIDC_CLIENT_SECRET> -n flyte
    kubectl create secret generic flyte-another-secret --from-literal=another_client_secret=<ANOTHER_CLIENT_SECRET> -n flyte

2. Reference the Secrets in
values.yaml
: Update your

values.yaml

to reference these secrets. You can use the

inlineSecretRef

to include multiple secrets.

Copy code

configuration:
      inlineSecretRef: flyte-oidc-secret,flyte-another-secret

3. Install or Upgrade Flyte: Use Helm to install or upgrade Flyte with the updated

values.yaml

Copy code

helm upgrade --install flyte flyteorg/flyte-core -n flyte --values values.yaml

This approach allows you to manage multiple secrets by referencing them in the

inlineSecretRef

. Would you like more detailed steps or a specific example? Sources: - https://github.com/flyteorg/flyte/pull/3807 - https://github.com/flyteorg/flyte/issues/2738 Note: I wasn’t able to find highly relevant data sources, but above are a few potentially relevant links. 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

4 Views

Open in Slack

Previous Next