Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Support Deployments based on Labeling of Worker Nodes

Open
#449 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
kubernetes

Research direction

No files, tests, or entry points are named. Start by locating the deployment configuration and the code that creates or schedules workloads, then determine how worker-node labels could be supplied per deployment. Done means workloads for each labeled deployment are placed only on matching worker nodes and the behavior is covered by appropriate tests.

Written by the indexing model from the issue text.

Description

Customer is planning to provision a big single ROSA cluster and deploy mutiple cloud pak for data on the same cluster.

They want to label worker nodes for the deployment before deployment and installation is invoked the expectation is that the workloads are pushed to specific worker nodes. that match the labels.

Example, If a specific set of worker nodes labele as CP4D_DEV and while deploying (CP4D) all workloads (pods) for CP4D_DEV deployment should be placed on CP4D_DEV worker nodes which match the labels.

Dominant language
Jinja
Stars
163
Forks
82
Avg merge
6m
Merged PRs (30d)
12

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from IBM/cloud-pak-deployer

All issues in IBM/cloud-pak-deployer

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.