chore: add kubefed fork

[hectorj2f]

Signed-off-by: Hector Fernandez [email protected]

What type of PR is this?

Chore
What this PR does/ why we need it:

While we are waiting to get kubernetes-retired/kubefed#1377 merged, we need to workaround that delay by getting our internal kubefed version based on v0.5.1.

Which issue(s) this PR fixes:

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Checklist

• If a chart is changed, the chart version is correctly incremented.
• The commit message explains the changes and why are needed.
• The code builds and passes lint/style checks locally.
• The relevant subset of integration tests pass locally.
• The core changes are covered by tests.
• The documentation is updated where needed.

[jimmidyson]

We can get kubernetes-retired/kubefed#1377 merged quickly (like tomorrow morning) I'm sure. Better than using a fork here imo.

[mhrabovcin]

This field is the reason we're adding fork of kubefed chart.

[mhrabovcin]

This will unblock https://jira.d2iq.com/browse/D2IQ-74314

[mhrabovcin]

@jimmidyson the upstream PR is against master branch. As @hectorj2f mentioned yakcl upgrade of kubefed would be non-trivial and it is not in the scope of our unidirectional work.

With merging this PR we'll get unblocked by temporarily using forked kubefed chart + custom built kubefed v0.5.2 containers. Once we have confidence in delivering unidirectional feature on time we'll invest time in upstream PR and bumping yakcl to use latest kubefed.

[joejulian]

I see that this is only a temporary fork so I'll approve despite my CR.

[gracedo]

This is only pulled in for yakcl right? Just wondering if it's easier to pull the chart directly into the kommander-federation local charts dir instead of using an extra m/charts fork, esp if this is just temporary

[mhrabovcin]

@gracedo I don't think we've considered this option. But you are right, this is temporary solution and the chart will be removed from our charts repo.