* feat: [Stable/Efs-Provisioner] add namespace to deployment/sa
Add the namespace information to deployment and serviaccount. this
Prevent helm3 to push the object to the current ns and not the one
Refered by the option "--namespace"
Signed-off-by: David Sabatie <david.sabatie@delair.aero>
* bump chart version
Signed-off-by: David Sabatie <david.sabatie@delair.aero>
* fix bad char in serviceaccount file
Signed-off-by: David Sabatie <david.sabatie@delair.aero>
* fix bad char in deployment
Signed-off-by: David Sabatie <david.sabatie@delair.aero>
* File system 'fs-12345678' does not exist
Fix issue related to default file system id:
```
W0109 08:06:08.407526 1 efs-provisioner.go:91] couldn't confirm that the EFS file system exists: FileSystemNotFound: File system 'fs-12345678' does not exist.
```
Signed-off-by: Dawid Malinowski <dawidmalina@gmail.com>
* Update Chart.yaml
Signed-off-by: Dawid Malinowski <dawidmalina@gmail.com>
* [stable/efs-provisioner] Default storage class to aws-efs
The current value for the efs-provisioner storage class is efs, which
differs from the default value in
https://github.com/kubernetes-incubator/external-storage/tree/master/aws/efs
and also in the AWS example page at
https://aws.amazon.com/premiumsupport/knowledge-center/eks-pods-efs/
This can be confusing when running examples and (automated) tests, so
I'm changing the value to "aws-efs" in the chart to be consistent with the references
in the storage provide and on the AWS example page.
Signed-off-by: Mariyan Dimitrov <mariyan.dimitrov@gmail.com>
* [stable/efs-provisioner] Bump chart version to 0.9.0
This version bump is related to the change in the default value of the
storage class that is created: from efs to aws-efs, so that it is
consistent with the reference in the storage provider and in the AWS
examples.
Signed-off-by: Mariyan Dimitrov <mariyan.dimitrov@gmail.com>
* [stable/efs-provisioner] add support for mounting with DNS
Signed-off-by: Kristof Szalontai <kszalontai@emarsys.com>
* [stable/efs-provisioner] typo
Signed-off-by: Kristof Szalontai <kszalontai@emarsys.com>
* fixing podAnnotations in deployment
pod annotations were getting overridden in deployment by deployment annotations.
Signed-off-by: Alessandro Grassi <alessandro.grassi01@gmail.com>
* bumped chart version
Signed-off-by: Alessandro Grassi <alessandro.grassi01@gmail.com>
* EFS ClusterRole - Grant access to 'endpoint' resources
Signed-off-by: Kevin Pullin <kevin.pullin@gmail.com>
* Do not create EFS deployment if default EFS id set
Signed-off-by: Kevin Pullin <kevin.pullin@gmail.com>
* Bump efs-provisioner chart version
Signed-off-by: Kevin Pullin <kevin.pullin@gmail.com>
* Fix indentation from github UI conflict edit
Signed-off-by: Kevin Pullin <kevin.pullin@gmail.com>
This commit enables passing in annotations via values for the
`efs-provisioner` chart and bumps the version to 0.1.3
Signed-off-by: Josh Myers <joshuajmyers@gmail.com>
* [stable/efs-provisioner] Add support for priorityClasses
Signed-off-by: Art3mK <artem@kayalaynen.ru>
* feat(deployment): disable deployment with default efsFileSystemId to prevent CI test failuersi
Signed-off-by: Art3mK <artem@kayalaynen.ru>