- github.com/gkampitakis/go-diff: [v1.3.2](https://github.com/gkampitakis/go-diff/tree/v1.3.2)
- github.com/gkampitakis/go-snaps: [v0.5.15](https://github.com/gkampitakis/go-snaps/tree/v0.5.15)
- github.com/goccy/go-yaml: [v1.18.0](https://github.com/goccy/go-yaml/tree/v1.18.0)
- github.com/joshdk/go-junit: [v1.0.0](https://github.com/joshdk/go-junit/tree/v1.0.0)
- github.com/maruel/natural: [v1.1.1](https://github.com/maruel/natural/tree/v1.1.1)

**How can I mitigate this prior to installing 1.5.5?**

1. Export existing PodSecurityPolicy objects:
  * `kubectl get podsecuritypolicies -o yaml > psp.yaml`
2. Review and delete any PodSecurityPolicy objects you do not want all pod-creating users to be able to use (NOTE: Privileged users that were making use of those policies will also lose access to those policies). For example:

* Use upgraded container-vm by default on worker nodes for GCE k8s clusters ...

yamanouchi.nagano.jp
yamashina.kyoto.jp
yamato.fukushima.jp
yamato.kanagawa.jp
yamato.kumamoto.jp
yamatokoriyama.nara.jp
yamatotakada.nara.jp
yamatsuri.fukushima.jp
yamaxun
yamazoe.nara.jp
yame.fukuoka.jp
yanagawa.fukuoka.jp
yanaizu.fukushima.jp
yandex
yandexcloud.net
yao.osaka.jp
yaotsu.gifu.jp
yasaka.nagano.jp
yashio.saitama.jp
yashiro.hyogo.jp
yasu.shiga.jp

yamanouchi.nagano.jp
yamashina.kyoto.jp
yamato.fukushima.jp
yamato.kanagawa.jp
yamato.kumamoto.jp
yamatokoriyama.nara.jp
yamatotakada.nara.jp
yamatsuri.fukushima.jp
yamaxun
yamazoe.nara.jp
yame.fukuoka.jp
yanagawa.fukuoka.jp
yanaizu.fukushima.jp
yandex
yandexcloud.net
yao.osaka.jp
yaotsu.gifu.jp
yasaka.nagano.jp
yashio.saitama.jp
yashiro.hyogo.jp
yasu.shiga.jp