Remove GitOps and Monitoring from the platform reference

Abierto
  • ¿Algo no está bien?
#167 3 comentarios 2 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Refactorización
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
aws, kubernetes
Área
cloud, devops, observability-sre

Línea de trabajo

Start by locating the AWS platform Composition and reading its GitOps and monitoring portions; the issue points to packages/gitops/argo-cd.yaml as a comparison. Done means those concerns are no longer bundled, while the EKS platform and AWS database configuration remain available.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement
What problem are you facing?

I'd like to adopt this reference platform for AWS but I find it difficult because it's currently addressing not only the creation of EKS clusters but also:

  • GitOps management
  • Monitoring tools

These, IMHO, should be removed from this Composition and let whoever wants to use this platform reference decide whether they want to use them or not and which tools they want to use.

For example, I'd rather use ArgoCD instead of Flux for GitOps and I found this issue https://github.com/upbound/platform-ref-aws/issues/22 where I agree with this comment:

We could consider doing this in a separate dedicated reference platform, instead of only as part of platform-ref-aws.
@vfarcic may have already done a good example of this work with https://github.com/vfarcic/devops-toolkit-crossplane/blob/master/packages/gitops/argo-cd.yaml.

Having Flux in this reference platform leaves me with no choice but either use Flux or give up using this platform reference.

Same could be for the Monitoring tools.

Instead, other configurations like upbound-configuration-aws-database are still AWS realm and they still fit into this reference platform.

How could Upbound help solve your problem?

It would be great if GitOps and Monitoring could be removed from this platform reference.

Lenguaje dominante
KCL
Estrellas
117
Forks
65
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de upbound/platform-ref-aws

Todos los issues de upbound/platform-ref-aws

Issues similares

Más issues de Cloud

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.