s/kubernextes/kubernetes/g

[daxxog]

Just a minor spelling thing.

[peterzhuamazon]

@DandyDeveloper @TheAlgo do we still want to follow the rules of every simple change need a version bump?

[DandyDeveloper]

Honestly, I don't think its my call anymore @peterzhuamazon I've said several times I don't believe spell checks / README updates need to worry about it chart version increments. It will fail in CI though but we can use our judgement on approval for merging.

But, I am certain people disagree with me.

[TheAlgo]

Honestly, I don't think its my call anymore @peterzhuamazon I've said several times I don't believe spell checks / README updates need to worry about it chart version increments. It will fail in CI though but we can use our judgement on approval for merging.

But, I am certain people disagree with me.

I remember quoting this in some PR , that we should not bump versions for README and spell checks and ignore CI failures or relax them.

Link : #152 (comment)

[peterzhuamazon]

Will wait a bit for this PR as I want to merge this right before another successful version bump so the pipeline will not show failure for a while.

[TheAlgo]

@daxxog Could you please sign off your commits because DCO checks are failing. Thanks

Ref : https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits

[daxxog]

@daxxog Could you please sign off your commits because DCO checks are failing. Thanks

Ref : https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits

Yes, I did this commit quick TTW and it is signed with github's GPG key.

I do have git configured properly with GPG on my workstation and can amend my commit to use that GPG key if it helps with your CI checks.

[peterzhuamazon]

@daxxog Could you please sign off your commits because DCO checks are failing. Thanks
Ref : https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits

Yes, I did this commit quick TTW and it is signed with github's GPG key.

I do have git configured properly with GPG on my workstation and can amend my commit to use that GPG key if it helps with your CI checks.

We are talking about using -s for signing DCO, not about -S signing GPG those are two things.
Could you git commit --amend --no-edit -s -S then push again?
Thanks.

[daxxog]

@peterzhuamazon Just pulled down branch and re-signed with my key on my workstation -- pushed changed back up to origin. Used the command you posted, thanks for the tip!

[peterzhuamazon]

@peterzhuamazon Just pulled down branch and re-signed with my key on my workstation -- pushed changed back up to origin. Used the command you posted, thanks for the tip!

Thanks. DCO passed.
Ignore other failures you did not change code so lint is complaining version changes.

Will leave this here a bit and merge it once another PR with version change ready, so your PR wont block a release.

Thanks.

[peterzhuamazon]

Thanks.