Current clusters have this warning:
W0531 18:10:31.675064 3773 azure.go:92] WARNING: the azure auth plugin is deprecated in v1.22+, unavailable in v1.25+; use https://github.com/Azure/kubelogin instead. To learn more, consult https://kubernetes.io/docs/reference/access-authn-authz/authentication/#client-go-credential-plugins

Also AKS release notes repeatingly highlight that. Cloudcontrol should be updated accordingly.
Guides are to be found here: https://github.com/Azure/kubelogin and i dont know... :/

hi,

need the >jq tool installed.... at least to use it for initial setup of AWS IAM ;)
i.e.
aws iam create-policy ... | jq -r ....

is it possible to add it during init?

...would be nice for M1 based Macs :)

Our config file is

version: "3"
services:
    cli:
        image: "ghcr.io/dodevops/cloudcontrol-azure:latest"
...
        environment:
            - "FEATURES=kubernetes terraform:1.7.5 helm:3.14.0 stern:1.28.0 fish kc kubectlnodeshell azcopy krew"
...
            - "USE_run=yes"
            - 'RUN_COMMANDS=source /terraform/cloudcontrol-template/christ_webshop/project_commands'

If we set up cloudcontrol with this configuration, “krew” will not be installed.

If i use a feature without given a version number and this feature has no "latest" or "default" fallback, cloudcontrol fails to start, but also does not provide a helpful error.

Example: I added feature "velero" without providing a version.
Cloudcontrol just failed with

2023/01/06 13:59:02 Error Downloading velero:
./ccc: exit status 1

With debug i saw, that it tried to download like this:
curl -f -s -L https://github.com/vmware-tanzu/velero/releases/download/v/velero-v-linux-amd64.tar.gz --output velero.tar.gz
which results in a 404.

Cloudcontrol should give a more speaking error in this case, also documentation should state which parameters are required where and which are optional.

Support https://k9scli.io/

The documentation is rendered faulty, see as an example https://github.com/dodevops/cloudcontrol#configuration-12:

• if there is a blank line in the yaml source, the rendered documentation intends the next text line all to the left
• sub bullet points (yaml source containing "*") are rendered as bullet points in the same top level

see:

2022/04/01 12:40:49 Error Authenticating against cluster atlasdc-cluster-01 in namespace tanzu-01: qemu-x86_64: Could not open '/lib64/ld-linux-x86-64.so.2': No such file or directory
./ccc: exit status 1

A special situation occured, where due to some reasons a login to the cloud is not possible (at least temporary).
It would be nice to be able to use cloud control without a cloud login, f.e. for plain terraform usage

Currently, when the CCC dies (because of an installation failure for example), the client just keeps on asking for status and doesn't show an error.

The client should display a prominent error message stating that it can not reach the server and suggest reading the logs.

A not existing terraform version causes the download not to fail (most probably it downloads some HTML then) and you get an unpack error, which is confusing:

2020/12/08 18:05:54 Downloading terraform...
2020/12/08 18:05:55 Unpacking terraform...
2020/12/08 18:05:55 Can not unpack terraform
./ccc: exit status 1

Please implement a verification, if the given terraform really exists or not.

Please incorporate direnv (maybe as switchable feature?). In special situations it is needed to quickly switch between certain credentials and direnv is very helpful for that.
Thanks.

Support Krew, the kubernetes kubectl plugin manager with the support to directly install plugins (might be possible to migrate kubectl node-shell to this as well)

Support kubectl node-shell

Since the feature certificates provides a means to add trusted certificate authorities to the CloudControl environment, the feature name should also reflect this purpose.

Please change the name og the feature to ca_certificates or tca.

Please add your opinions

As discussed with @dploeger on a call:

• add "certificates" feature
• expects a bind mounted folder, should fail if folder not there
• looks for *.pem files in that folder
• adds it to the certs to the root-ca collection specific to the flavours base-image OS way

Looks like the tokens for azure now expire pretty fast - a "relogin" script (similar to tanzu flavor) would help, so one does not have to re-init the whole container.

Support overriding the message that gets displayed upon entering the container, so projects can put some hints on how to work inside the container into the compose file.

If feature fish is used on simple flavour, every command "enter" goes like this:

fish: Unknown command: git
~/.config/fish/functions/__sf_section_dir.fish (line 1):
command git rev-parse --show-toplevel 2>/dev/null
^
in command substitution
	called on line 30 of file ~/.config/fish/functions/__sf_section_dir.fish
in function '__sf_section_dir'
	called on line 1 of file ~/.config/fish/functions/fish_prompt.fish
in function 'fish_prompt'
in command substitution
~/.config/fish/functions/__sf_section_dir.fish (line 30): Unknown command
	set -l git_root (command git rev-parse --show-toplevel 2>/dev/null)
	                ^
in function '__sf_section_dir'
	called on line 1 of file ~/.config/fish/functions/fish_prompt.fish
in function 'fish_prompt'
in command substitution

Fix the _fish in the setup wizard

Support azCopy as a feature

See

Tag "latest" does not exist. See https://hub.docker.com/r/dodevops/cloudcontrol-simple/tags
Setting it to "main" instead of "latest" works.

At first: thanks for creating cloudcontrol. It is useful for us!

I would like to suggest the cmctl tool for integration into cloudcontrol.
Source: https://cert-manager.io/docs/reference/cmctl/

This makes it much easier, for example, to renew letsencrypt certificates before they expire.
Example:

./cmctl_linux_amd64 renew -n myNamespace myCertificateName
Manually triggered issuance of Certificate myNamespace/myCertificateName

FeatureRequest

VMWare Tanzu offers a Tanzu CLI and other tools which provide support for the work with the Tanzu resources.

Please implement the installation as a feature for the Tanzu flavor.

Support fetching kubernetes admin credentials in the Azure flavour.

Abstract:

Instead of configuring every feature as an individual environment setting consolidate them together with the desired version in just one setting.

Example:

Old:

environment:
    - "USE_kubernetes=yes"
    - "USE_terraform=yes"
    - "USE_kc=yes"
    - "USE_fish=yes"
    - "USE_packer=yes"
    - "PACKER_VERSION=1.7.8"

New:

environment:
    - "FEATURES='kubernetes, terraform, kc, packer:1.7.8, fish, helloWorld'"

Omitting the version will then result in a defined way, e.g. the latest version or a maintainers choice preset.