devopshivehq/devops-coding-mentorship

Helping DevOps Engineers to write more code

devops-coding-mentorship's Issues

Support KRM in Kustomize plugin - TemplateTransformer

Intro

Kustomize (the official tool to create K8s IaC) adopted the new Kubernetes declarative configurations known as KRM Functions. The new style is used as a unified way to interact with Kustomize plugins. There are 2 ways to use KRM in the plugins: Containerized KRM Functions and Exec KRM functions.

Not all Kustomize plugins adopted the new format; hence the goal of this task is to support the new method in existing plugins, namely, TemplateTransformer.

Acquired Skills

By doing this task, you will gain the following skills:

• Golang coding skills.
• Kustomize plugin ecosystem.
• Unerstanding of Kubernetes Resource Model (KRM).

The Challange

Support KRM in [TemplateTransformer](https://github.com/joshdk/template-transformer Kustomize plugin.

The Task

• Create an issue in TemplateTransformer to propose supporting KRM.
• Fork the TemplateTransformer repo and create a new branch to work on the task.
• Create a PR in the forked repo and assign me (@aabouzaid) as a reviewer.

Notes and Tips

• Get into KRM: Kustomize Enhancement with KRM Functions
• There are 2 libs to support KRM, kpt-functions-sdk/go/fn from Google and another kyaml/fn/framework from the Kustomize project. Please use the one from Kustomize. It makes it easy to write KRM functions.
• A good example of using kyaml/fn/framework (the one from Kustomize) is kustomize-kubeconformvalidator.

Related Links

• TBA

Support KRM in Kustomize plugins

Intro

Kustomize (the official tool to create K8s IaC) adopted the new Kubernetes declarative configurations known as KRM Functions. The new style is used as a unified way to interact with Kustomize plugins. There are 2 ways to use KRM in the plugins: Containerized KRM Functions and Exec KRM functions.

Acquired Skills

By doing any of the tasks in this epic, you will gain the following skills:

• Golang coding skills.
• Kustomize plugin ecosystem.
• Unerstanding of Kubernetes Resource Model (KRM).

The Challange

Support KRM in Kustomize plugins that don't support it yet.

The Tasks

Check Awesome Kustomize to find the plugins that don't support KRM yet.
The following are the open tasks already.

• #6
• #7
• #2

more detailes for implementation

I like to be involved as a mentor for: Helm, Bash, Python, Golang
but I still do not understand how to do that, I guess you may create an online session to share your idea and add more details for the implementation.

Support KRM in Kustomize plugin - Secretize

Intro

Kustomize (the official tool to create K8s IaC) adopted the new Kubernetes declarative configurations known as KRM Functions. The new style is used as a unified way to interact with Kustomize plugins. There are 2 ways to use KRM in the plugins: Containerized KRM Functions and Exec KRM functions.

Not all Kustomize plugins adopted the new format; hence the goal of this task is to support the new method in existing plugins, namely, Secretize.

Acquired Skills

By doing this task, you will gain the following skills:

• Golang coding skills.
• Kustomize plugin ecosystem.
• Unerstanding of Kubernetes Resource Model (KRM).

The Challange

Support KRM in Secretize Kustomize plugin.

The Task

• Create an issue in Secretize to propose supporting KRM.
• Fork the Secretize repo and create a new branch to work on the task.
• Create a PR in the forked repo and assign me (@aabouzaid) as a reviewer.

Notes and Tips

• Get into KRM: Kustomize Enhancement with KRM Functions
• There are 2 libs to support KRM, kpt-functions-sdk/go/fn from Google and another kyaml/fn/framework from the Kustomize project. Please use the one from Kustomize. It makes it easy to write KRM functions.
• A good example of using kyaml/fn/framework (the one from Kustomize) is kustomize-kubeconformvalidator.

Related Links

• TBA

Install asdf plugins declaratively

Enhance plugin management in asdf.

There is already an open PR for that change asdf-vm/asdf#1204, however, it's unclear when it will be merged.

For that reason, we need to make it a plugin for asdf (i.e. a plugin to manage plugins).

Support KRM in Kustomize plugin - PolicyGenerator

Intro

Kustomize (the official tool to create K8s IaC) adopted the new Kubernetes declarative configurations known as KRM Functions. The new style is used as a unified way to interact with Kustomize plugins. There are 2 ways to use KRM in the plugins: Containerized KRM Functions and Exec KRM functions.

Not all Kustomize plugins adopted the new format; hence the goal of this task is to support the new method in existing plugins, namely, PolicyGenerator.

Acquired Skills

By doing this task, you will gain the following skills:

• Golang coding skills.
• Kustomize plugin ecosystem.
• Unerstanding of Kubernetes Resource Model (KRM).

The Challange

Support KRM in PolicyGenerator Kustomize plugin.

The Task

• Create an issue in PolicyGenerator to propose supporting KRM.
• Fork the PolicyGenerator repo and create a new branch to work on the task.
• Create a PR in the forked repo and assign me (@aabouzaid) as a reviewer.

Notes and Tips

• Get into KRM: Kustomize Enhancement with KRM Functions
• There are 2 libs to support KRM, kpt-functions-sdk/go/fn from Google and another kyaml/fn/framework from the Kustomize project. Please use the one from Kustomize. It makes it easy to write KRM functions.
• A good example of using kyaml/fn/framework (the one from Kustomize) is kustomize-kubeconformvalidator.

Related Links

• TBA

Tidy up Camunda Platform Helm notes

The Camunda Platform Helm notes could be better.

By doing this task, you will gain the following skills:

• Basic Helm chart development.

The Challange

Camunda Platform Helm chart has multiple components (applications), and some users don't need all components, so if one of the components is disabled, it should not show in the Helm notes.

The Task

You need to add conditions in the Connecting to Web apps section, so if one of the apps is disabled, it should not appear in the notes.

Also you need to add the Ingress host if it's enabled (it's not mentioned in the notes at all).

Notes

The Helm chart note is not rendered via the helm template [...] command; you need to find a different way to debug it.

Links

• Add Ingress details into NOTES.txt - camunda/camunda-platform-helm#736