Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

As a EDP User, I want to have static cluster resources name #12

Closed
MykolaMarusenko opened this issue May 9, 2023 · 1 comment
Closed
Assignees
Labels
enhancement New feature or request

Comments

@MykolaMarusenko
Copy link
Contributor

Currently we have random values for example for name of service.

Image

Acceptance Criteria:

  • headlamp UI always create kind: Application with correct spec to deploy helm application with with static helm release name;
  • get release name from /deploy-templates/Chart.yaml or from codeabase name;
  • provide functional to redefine release name;

https://argo-cd.readthedocs.io/en/stable/user-guide/helm/
argoproj/argo-cd#1066

Investigate fullnameOverride parameter in values.yaml.

@MykolaMarusenko MykolaMarusenko converted this from a draft issue May 9, 2023
@MykolaMarusenko MykolaMarusenko added the enhancement New feature or request label May 9, 2023
@Rolika4 Rolika4 moved this from Todo to In Progress in KubeRocketCI (EPAM Delivery Platform) May 15, 2023
@Rolika4 Rolika4 moved this from In Progress to Done in KubeRocketCI (EPAM Delivery Platform) May 19, 2023
@Rolika4
Copy link

Rolika4 commented May 19, 2023

In patch [EPMDEDP-11961] was implemented static resources name for all component in a cluster. Early, the helm template during deployment into the cluster was created with a hash at the end of the name.

Now all templates are created with the names that are defined in the chart.yaml file, in the name block.

For example for Chart.yaml:

apiVersion: v2
name: python38
description: A Helm chart for Kubernetes

Service name: python38
Image
Endpoint name: python38
Image
Deployment name: python38
Image

@Rolika4 Rolika4 closed this as completed May 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

No branches or pull requests

2 participants