lyft / lyft/flinkk8soperator

Custom Deployments

Open
#193 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
581
Forks
153
PR merge metrics
No merged PRs in 30d

Description

Is there a way to customize the deployment generated by the operator. In particular adding init containers to do setup work required by our environment? We are generating job jars dynamically, and for security reasons can not create new images per job. We want an init container to copy the jar to the proper place in /opt before the job starts with the standard image.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

The issue does not name specific files or tests. Start by tracing how the operator generates the Kubernetes deployment for the standard image, then determine how custom init containers and dynamically generated job JARs should be represented. Done means the requested deployment customization is supported and its behavior is covered by appropriate tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
devops, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.