globocom / globocom/enforcement
EKS Cluster Source
Open
enhancement
- Dominant language
- Python
- Stars
- 13
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
The purpose of this task is to implement support for the origin of the EKS (Elastic Kubernetes Service) cluster.
Access information as a service account token will be passed on to the secret that the cluster source must know how to read.
The custom resource that contains the EKS source cluster should look like this:
```yaml
source:
secretName: eks-secret
eks:
tags: {}
ignore:
- cluster1
- cluster2
- cluster3
```
The rules for reading the secret performed by the cluster source must follow the requirements specified in issue #4
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.