Skip to content

Which structure should I use in my scenario #1

@wokwong

Description

@wokwong

I have multiple applications that share the same chart, which is stored in harbor. The docker images for these applications are stored in harbor. The values.yaml for these applications is created by environment and stored in a separate git repo.
So, I need to watch the following changes at the same time

  • image (in harbor)
  • values.yaml (in git repo)
  • chart (in chart registry with harbor)

The values repo structure looks like this:

$ tree 
.
├── README.md
├── app1
│   ├── dev
│   │   └── values.yaml
│   ├── test
│   │   └── values.yaml
│   ├── uat
│   │   └── values.yaml
├── app2
│   ├── dev
│   │   └── values.yaml
│   ├── test
│   │   └── values.yaml
│   ├── uat
│   │   └── values.yaml
......

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions