hazelcast / hazelcast/hz-docs

Docs: Feedback for Deploying Hazelcast Open Source on Kubernetes with Helm

Open
#991 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
11
Forks
112
Avg merge
20h 29m
Merged PRs (30d)
19

Description

Hi, I have some feedback about [this page](https://github.com/hazelcast/hz-docs/edit/main/docs/modules/kubernetes/pages/helm-hazelcast-chart.adoc)

We have updated the Hazelcast with helm and got the issue:
Screenshot 2024-02-02 at 10 44 00 AM
/

```
Warning: The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Packaging chart 'charts/hazelcast'...
Error: no repository definition for https://hazelcast-charts.s3.amazonaws.com/
Usage:
cr package [CHART_PATH] [...] [flags]
```

We ran the command we got this:
```
/❯ helm dep update
Getting updates for unmanaged Helm repositories...
...Successfully got an update from the "https://hazelcast-charts.s3.amazonaws.com/" chart repository
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "bitnami" chart repository
Update Complete. ⎈Happy Helming!⎈
Saving 1 charts
Downloading hazelcast from repo https://hazelcast-charts.s3.amazonaws.com/
Deleting outdated charts```
```

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading docs/modules/kubernetes/pages/helm-hazelcast-chart.adoc and compare its documented Helm workflow with the reported cr package error and helm dep update output. Reproduce the shown commands, identify which documented step or prerequisite is unclear, and finish when the page describes a working workflow that addresses the reported error.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, helm, kubernetes
Domain
devops, documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.