kong2kic changes after code review

[battlebyte]

This change incorporates the suggestions from
@Gabriele Gerbino

@travenichka

@michal

@Greg

• Use of KongUpstreamPolicy in 3.x
• Use labels for credential type in 3.x
• No status or metadata.creationTimestamp fields are in the output

The new command interface is:

Convert Kong configuration files to Kong Ingress Controller (KIC) manifests.

The kong2kic subcommand transforms Kong’s configuration files, written in the deck format,
into Kubernetes manifests suitable for the Kong Ingress Controller. By default kong2kic generates
manifests for KIC v3.x using the Kubernetes Gateway API. Only HTTP/HTTPS routes are supported.

Usage:
  deck file kong2kic [flags]

Flags:
      --class-name string    Value to use for "kubernetes.io/ingress.class" ObjectMeta.Annotations and for
                             		"parentRefs.name" in the case of HTTPRoute. (default "kong")
  -f, --format string        output file format: json or yaml. (default "yaml")
  -h, --help                 help for kong2kic
      --ingress              Use Kubernetes Ingress API manifests instead of Gateway API manifests.
      --kicv2                Generate manifests compatible with KIC v2.x.
  -o, --output-file string   Output file to write. Use - to write to stdout. (default "-")
  -s, --state string         decK file to process. Use - to read from stdin. (default "-")

[mheap]

Merging in to the kic branch for final review

[mheap]

Aha! I'm not on @Kong/team-deck. Could someone please merge? This is targeting the kic branch, not main and we'll do a final review on #1050

[Tieske]

looking at the commits, it should be rebased on the kic branch first.

[battlebyte]

My battlebyt/kic fork is already in sync with Kong:kic branch, correct?

[czeslavo]

My suggestion regarding dropping status and creationTimestamp fields has been addressed. 👍 I'm not sure about failing tests though - as I can see they're passing on #1050 so probably there's something to be fixed here before merging to kic branch.

[CLAassistant]

All committers have signed the CLA.

[Tieske]

My battlebyt/kic fork is already in sync with Kong:kic branch, correct?

Doesn't look like it. If you look at the commits in this PR, they have a lot of work that is also in the base branch.

[battlebyte]

Sorry @Tieske , you're right. This pull request now has 1 squashed commit that continues after the last commit (f419701) in PR #1050.

[Tieske]

@battlebyte I fixed the linter issues, and then accidentally merged this PR because its name is the same as the base branch.

Please ensure you change the branch name next time. (if you have no other pending work, my suggestion would be to delete your clone and create a new one all together)