https://prefect.io
Join Slack
For k8s agents, do I need to use a service account for them?
# ask-community
w
For k8s agents, do I need to use a service account for them?
Having a hard time looking at this agent deployment configuration and seeing • 
PREFECT__CLOUD__AGENT__AUTH_TOKEN
• 
PREFECT__CLOUD__API_KEY
• 
PREFECT__CLOUD__TENANT_ID
• 
SERVICE_ACCOUNT_NAME
z
SERVICE_ACCOUNT_NAME
is used to specify the K8s service account that the job should be submitted with
PREFECT__CLOUD__AGENT__AUTH_TOKEN
is legacy support for auth tokens, you should not need this unless you are running flows pre 0.15.x
PREFECT__CLOUD__API_KEY
is the API key for the Prefect Service Account / User that you want to use to run flows
w
Cool, so I can leave auth token blank then
z
PREFECT__CLOUD__TENANT_ID
is for if a user API key is used since it can span multiple tenants
w
@Zanie what is 
IMAGE_PULL_SECRETS
sorry, I'm trying to set this up with kustomize and kubectl so I can deploy it easily in our environment
t
IMAGE_PULL_SECRETS are used to authenticate with private image repos
all k8s workloads have serviceaccounts, so if you don't specify one, the agent's jobs will spin up with the 
default
serviceaccount
it is not important to worry about kubernetes serviceaccounts unless you have specific RBAC auth or security set up around them inside the cluster
w
ya nothing too crazy AFAIK. I play ops in my free time.
marvin 1
Just trying to replace celery
Open in Slack
PreviousNext
Powered by

Prefect Community

Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Powered by