Support Kubernetes 1.24

[masa213f]

#55
Support Kubernetes 1.24 and update dependencies.

• Update go modules.
  • Update ginkgo to v2
• Update build and test tools.
  • Stop using nilerr.
• Update actions.
• Build with go 1.18

And I update e2e test due to the following change in k8s 1.24.

https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.24.md#urgent-upgrade-notes

The LegacyServiceAccountTokenNoAutoGeneration feature gate is beta, and enabled by default. When enabled, Secret API objects containing service account tokens are no longer auto-generated for every ServiceAccount. Use the TokenRequest API to acquire service account tokens, or if a non-expiring token is required, create a Secret API object for the token controller to populate with a service account token by following this guide.

Signed-off-by: Masayuki Ishii [email protected]

[masa213f]

ginkgo said as follows.

--ginkgo.failFast is deprecated, use --ginkgo.fail-fast instead
Learn more at:https://onsi.github.io/ginkgo/MIGRATING_TO_V2#changed-command-line-flags

[morimoto-cybozu]

The creation of sn1/test should be waited with Eventually().
This Consistently() can fail if the creation of sn1/test ServiceAccount is delayed.
As far as I know kubectl apply above is synchronous only for subroot1/test, not for sn1/test.

Once sn1/test is created, it would be enough to check the contents of the ServiceAccount just once because we know that the ServiceAccount is created atomically.
To test the stability of sn1/test seems excess for me.

You can check the contents even inside Eventually() as done in the previous It().

[masa213f]

This Consistently() can fail if the creation of sn1/test ServiceAccount is delayed.

Thank you. That's true. If the test machine has low spec, this test may be fail.
I'll use Eventually().

[morimoto-cybozu]

LGTM

[kmdkuk]

LGTM