• ❌ The email address for the commit (9acf252) is not linked to the GitHub account, preventing the EasyCLA check. Consultthis Help Article andGitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA,please submit a support request ticket.

Welcome@MatthewFletcher!

It looks like this is your first PR tokubernetes/kompose 🎉. Please refer to ourpull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment.Here is the bot commands documentation.

You can also check if kubernetes/kompose hasits own contribution guidelines.

You may want to refer to ourtesting guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow therecommended escalation practices. Also, for tips and tricks in the contribution process you may want to read theKubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[APPROVALNOTIFIER] This PR isAPPROVED

This pull-request has been approved by:cdrage,MatthewFletcher

The full list of commands accepted by this bot can be foundhere.

The pull request process is describedhere

Hi@MatthewFletcher !

As soon as you update your CLA signing, this should auto-merge in. Thanks for the changes!

Gentle ping@MatthewFletcher

@cdrage tried it again, let me know if that works.

@cdrage tried it again, let me know if that works.

It's not sorry :( and I can't seem to re-trigger it.

Could you maybe rebase your PR against main and re-push it? It'll retrigger the EasyCLA CI.

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity,lifecycle/stale is applied
• After 30d of inactivity sincelifecycle/stale was applied,lifecycle/rotten is applied
• After 30d of inactivity sincelifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with/remove-lifecycle stale
• Close this PR with/close
• Offer to help out withIssue Triage

Please send feedback to sig-contributor-experience atkubernetes/community.

/lifecycle stale

The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity,lifecycle/stale is applied
• After 30d of inactivity sincelifecycle/stale was applied,lifecycle/rotten is applied
• After 30d of inactivity sincelifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with/remove-lifecycle rotten
• Close this PR with/close
• Offer to help out withIssue Triage

Please send feedback to sig-contributor-experience atkubernetes/community.

/lifecycle rotten

Going to close this for now, sorry! Just curating through our PR's.

After the CLA is signed, I'll be able to merge, please feel free to re-open!