Support to serialize MicroTime fields

[uesyn]

Some Kubernetes objects expect to have date fields represented RFC3339 format with microsecond.
However, Kubernetes is unable to represent microsecond field in openapi schema.
ref: kubernetes/kubernetes#97904

In this PR, patch the kubernetes/gen which generate clients based on the open api schema generated by kubernetes, and define V1MicroTime to represent microseconds.
I confirmed the below code works.

import * as k8s from "@kubernetes/client-node";

async function main(): Promise<void> {
  const config = new k8s.KubeConfig();
  config.loadFromDefault();

  const cli = config.makeApiClient(k8s.CoordinationV1Api);
  await cli.createNamespacedLease("default", {
    metadata: {
      name: "foo",
      namespace: "default",
    },
    spec: {
      acquireTime: new k8s.V1MicroTime(),
      holderIdentity: "foo",
    },
  });
}

(async () => {
  await main();
})()

ref: #828

[brendandburns]

@uesyn thank you for the PR!

Instead of patching the pre-process python script, can you just send a PR to this repo:
https://github.com/kubernetes-client/gen/blob/master/openapi/preprocess_spec.py

I'm a maintainer on that repo so I can get that PR merged pretty quickly.

That will be cleaner/easier to understand.

Once that PR is in, we can rebase this one to pick up those changes and then merge this one.

Thanks!

[uesyn]

@brendandburns Thank you for the comment!

I created the PR for kuberentes/gen!

I checked kubernetes/gen's master branch, and found that it's typescript's generatorName is typescript(for 1.x.y versions) not typescript-node(for 0.x.y versions).
ref: kubernetes-client/gen#219

Therefore, to generate codes with typescript-node, we need to create a new branch from this commit, and cherry-pick the PR to it.

[uesyn]

Once that PR is in, we can rebase this one to pick up those changes and then merge this one.

I rebased this PR in advance that the PR is merged.
I dropped the commit to patch kubernetes/gen.
Should I drop the commit which regenerate the codes too?

[brendandburns]

Thanks I LGTM'd the gen PR. You're right that we need to branch and pull it back to the commit that we use for generation, but for now let's just merge this PR also.

[uesyn]

@brendandburns
Thank you for the review of the kubernetes/gen PR!
I rebased this PR, and make it contain only V1MicroTime type definition. PTAL😄

[brendandburns]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: brendandburns, uesyn

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [brendandburns]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[brendandburns]

I think the next step is to run the Github action to regenerate the code.

I think that we should edit the github action to cherry-pick the gen commit before we run the generation.

[uesyn]

@brendandburns
I have the same understanding.
If you don't mind, I will make PR 😄.