operator-framework / operator-framework/operator-lib

Prune package?

Open
#236 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
41
Forks
42
Avg merge
8d 8h
Merged PRs (30d)
4

Description

In the operator sdk example for resource pruning referencing this lib, it shows using the Config{} struct and it doesn't line up at all with what i'm seeing here. Has this api changed?

Contributor guide

Open the 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.

Research direction

Compare the Operator SDK resource-pruning example that uses Config{} with the current operator-lib API. Start by locating the example and the current Config definition; done means the example matches the library, or the API discrepancy and required usage are documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.