siderolabs / siderolabs/docs

Broken vmware documentation for v1.14

Open Beginner friendly
#752 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
MDX
Stars
11
Forks
76
Avg merge
3d 5h
Merged PRs (30d)
26

Description

here: https://docs.siderolabs.com/talos/v1.14/platform-specific-installations/virtualized-platforms/vmware

The first link is missing the content:

curl -fsSLO https://raw.githubusercontent.com/siderolabs/docs/main/static/talos/v1.14/vmware/cp.patch.yaml

here: https://github.com/siderolabs/docs/tree/main/static/talos

then using the cp.patch from v.13 curl -fsSLO https://raw.githubusercontent.com/siderolabs/docs/main/static/talos/v1.13/vmware/cp.patch.yaml
Setting the cp.patch.yaml as:

- op: add
  path: /machine/network
  value:
    interfaces:
    - interface: eth0
      dhcp: true
      vip:
        ip: 192.168.1.222

and running talosctl gen config vmware-test https://192.168.1.222:6443 --config-patch-control-plane @cp.patch.yaml as explained in the documentation I got this error:

generating PKI and tokens
failed to generate config bundle: error patching control plane configs: JSON6902 patches are not supported for multi-document machine configuration

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 with the v1.14 VMware documentation page and compare its first link with the files under static/talos, especially the v1.13 and v1.14 VMware paths. Check the cp.patch.yaml example against the reported talosctl gen config command and its multi-document patch error. Done means the v1.14 link and patch instructions work consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
yaml
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
72/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.