You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Magnus Runesson (Jira)" <ji...@apache.org> on 2019/12/07 12:26:00 UTC
[jira] [Resolved] (AIRFLOW-4156) KubernetesPodOperator does not
support set security context
[ https://issues.apache.org/jira/browse/AIRFLOW-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Magnus Runesson resolved AIRFLOW-4156.
--------------------------------------
Fix Version/s: 1.10.6
Resolution: Fixed
It is fixed now.
> KubernetesPodOperator does not support set security context
> -----------------------------------------------------------
>
> Key: AIRFLOW-4156
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4156
> Project: Apache Airflow
> Issue Type: Improvement
> Components: operators
> Affects Versions: 1.10.2
> Environment: kubernetes
> Reporter: Magnus Runesson
> Priority: Major
> Labels: kubernetes
> Fix For: 1.10.6
>
>
> Good praxis running containers is to not run them as root nor run with a writable root-filesystem. To be able to restrict this on pods launched by the KubernetesPodOperator one must be able to set [security context|https://kubernetes.io/docs/tasks/configure-pod-container/security-context/]. Many hardened Kubernetes clusters require this to be set.
> WIP patch, currently missing tests:
> https://github.com/mrunesson/airflow/tree/feat-k8s-security-context
--
This message was sent by Atlassian Jira
(v8.3.4#803005)