upgrade dataset to 0.1.10

[usernameisnull]

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on a routine version upgrade for the dataset Helm chart. It systematically updates all relevant version identifiers and associated image tags to 0.1.10, ensuring that deployments using this chart will now utilize the latest specified release of the dataset application and its components. This change is primarily for maintenance and consistency.

Highlights

• Helm Chart Version Upgrade: The dataset Helm chart and its nested components have been upgraded from version 0.1.9 to 0.1.10.
• Image Tag Updates: The image tags for the dataset-controller and dataset-data-loader components have been updated to v0.1.10 across various values.yaml files.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• charts/dataset/config
  • Updated the exported VERSION variable to 0.1.10.
• charts/dataset/dataset/Chart.yaml
  • Updated the main chart's version to 0.1.10.
  • Updated the dataset dependency version to 0.1.10.
• charts/dataset/dataset/charts/dataset/Chart.yaml
  • Updated the nested chart's version to 0.1.10.
• charts/dataset/dataset/charts/dataset/values.yaml
  • Updated the dataset-controller image tag to v0.1.10.
  • Updated the dataset-data-loader image tag to v0.1.10.
• charts/dataset/dataset/values.yaml
  • Updated the dataset-controller image tag to v0.1.10.
  • Updated the dataset-data-loader image tag to v0.1.10.

Activity

• No human activity has been recorded on this pull request yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

The pull request successfully updates the version of the dataset chart and its components to v0.1.10 across various configuration and Helm chart files. However, there is an inconsistency in charts/dataset/dataset/Chart.yaml where the chart's own version was not updated, while its dependency's version was. This should be corrected to ensure the chart metadata accurately reflects the new version.

[Frapschen]

/lgtm

[fkajerry]

/lgtm

[Frapschen]

/approve