[
https://issues.apache.org/jira/browse/AIRFLOW-3609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16731649#comment-16731649
]
ASF GitHub Bot commented on AIRFLOW-3609:
-
dimberman commented on pull request #4417: [AIRFLOW-3609] Fix bug in persistent
volumes readWriteMany
URL: https://github.com/apache/incubator-airflow/pull/4417
Make sure you have checked _all_ steps below.
### Jira
- [ ] My PR addresses the following [Airflow
Jira](https://issues.apache.org/jira/browse/AIRFLOW/) issues and references
them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR"
- https://issues.apache.org/jira/browse/AIRFLOW-3609
- In case you are fixing a typo in the documentation you can prepend your
commit with \[AIRFLOW-XXX\], code changes always need a Jira issue.
### Description
- [ ] Here are some details about my PR, including screenshots of any UI
changes:
When running integration tests on a k8s cluster vs. Minikube
I discovered that we were actually using an invalid permission
structure for our persistent volume. This commit fixes that.
### Tests
- [ ] My PR adds the following unit tests __OR__ does not need testing for
this extremely good reason:
### Commits
- [ ] My commits all reference Jira issues in their subject lines, and I
have squashed multiple commits if they address the same issue. In addition, my
commits follow the guidelines from "[How to write a good git commit
message](http://chris.beams.io/posts/git-commit/)":
1. Subject is separated from body by a blank line
1. Subject is limited to 50 characters (not including Jira issue reference)
1. Subject does not end with a period
1. Subject uses the imperative mood ("add", not "adding")
1. Body wraps at 72 characters
1. Body explains "what" and "why", not "how"
### Documentation
- [ ] In case of new functionality, my PR adds documentation that describes
how to use it.
- When adding new operators/hooks/sensors, the autoclass documentation
generation needs to be added.
- All the public functions and the classes in the PR contain docstrings
that explain what it does
### Code Quality
- [ ] Passes `flake8`
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> PersistentVolumes in k8s CI have incorrect permissions
> --
>
> Key: AIRFLOW-3609
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3609
> Project: Apache Airflow
> Issue Type: Bug
> Components: kubernetes
>Reporter: Daniel Imberman
>Assignee: Daniel Imberman
>Priority: Minor
>
> When running integration tests on a k8s cluster vs. Minikube
> I discovered that we were actually using an invalid permission
> structure for our persistent volume. This commit fixes that.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)