Release/v0.10.0

[bourgeoisor]

This PR releases Online Boutique v0.10.0.

Additionally, it brings the Helm chart templates up to par with any Kustomize base changes that has happened since December 2022. [diff]

I also updated the releasing docs [staging].

Closes #2496

• Checks are all passing
• Deploy on the production environment
• Manually test
• Draft & publish release notes [draft]
• Announce release

[github-actions]

🚲 PR staged at http://34.172.167.143

[NimJay]

Question: Was this intentional?

[bourgeoisor]

Yes, service accounts are a good best practice and we decided to turn them on by default in kustomize-- might as well reflect that in Helm as well.

[NimJay]

Sounds good! We should eventually (out-of-scope for this PR):

1. remove the ServiceAccounts Kustomize component + add it to the default manifests sorry, forgot we already did this!
2. remove the option to remove ServiceAccounts in Helm (i.e., create: false seems unnecessary).

[bourgeoisor]

Created #2508

[bourgeoisor]

This release works in the staging / PRs cluster, but the adservice is stuck in a segfault crash loop on the production cluster:

# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007fb423c7e522, pid=1, tid=16
#
# JRE version:  (21.0.2+13) (build )
# Java VM: OpenJDK 64-Bit Server VM (21.0.2+13-LTS, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, serial gc, linux-amd64)
# Problematic frame:
# C  [profiler_java_agent.so+0x897522]  std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::assign(char const*)+0xc
#
# Core dump will be written. Default location: /core.%e.1.%t
#
# Can not save log file, dump to screen..
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007fb423c7e522, pid=1, tid=16
#
# JRE version:  (21.0.2+13) (build )
# Java VM: OpenJDK 64-Bit Server VM (21.0.2+13-LTS, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, serial gc, linux-amd64)
# Problematic frame:
# C  [profiler_java_agent.so+0x897522]  std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::assign(char const*)+0xc
#
# Core dump will be written. Default location: /core.%e.1.%t

Edit 1: I spun up another random cluster and it deployed fine there too. The only cluster with that issue seems to be the GKE release cluster.

Edit 2: I upgraded both the control plane and node pool on the release cluster to the latest version and still running into that segfault crash loop.

[NimJay]

Regarding the adservice error: we may need to create a new GKE (autopilot) cluster for production — similar to #2418.
We can do that after this pull-request has been merged.

[NimJay]

Thanks so much for doing this, @bourgeoisor! 👏

File changes look good.
I see all v0.10.0 images in container registry + the Helm v0.10.0 artifact. ✅
Staging URL works. ✅
Draft release notes look good. Dang, you even counted the dependency updates. 💯

Issue: Since this contains a lot of edits to the Helm templates/manifests, we should check that Helm deploys successfully:

helm upgrade onlineboutique oci://us-docker.pkg.dev/online-boutique-ci/charts/onlineboutique \
    --install

We can address everything about deploying to the production cluster after this PR has been merged.

[bourgeoisor]

Created #2509 for recreating the release GKE cluster.

[github-actions]

🚲 PR staged at http://34.172.167.143