Itay Brandes comments

Results 33 comments of


                                            Itay Brandes

Occasionally managed rke1 cluster re-provisioning fails using terraform provider

I get this sometimes on brand new clusters.

feat(helm): add ability for --dry-run to do lookup functions

I'm also looking forward for this, and wish to help if any help is needed.

[BUG] [ERROR] waiting for cluster (c-cgq6f) to be updated: unexpected state 'error' while upgrading a RKE cluster from 1.23.10 to 1.24+

This seem to still happen when upgarding from 1.25 to 1.26 (rancher 2.7.9)

Using regex with escaped characters crashes with "yaml.scanner.ScannerError: while scanning a double-quoted scalar"

This is still relevant. Fix using sed: `sed -i 's|" \\"" + str(value) + "\\"\\n"|" \\"" + str(value).replace("\\\\", "\\\\\\\\") + "\\"\\n"|g' $(python -c 'import os.path, aiohttp_swagger; print(os.path.dirname(aiohttp_swagger.__file__))')/helpers/builders.py`

Support for "9995:9995/tcp"

The parser won't parse - 7000:7000/tcp correctly.

[RFE] useInstanceMetadataHostname not available in Terraform rancher2_cluster resource

That's a real issue. I've hacked my way around by monkey patching the terraform provider and compiling it myself.

[RFE] useInstanceMetadataHostname not available in Terraform rancher2_cluster resource

Still relevant.

[RFE] useInstanceMetadataHostname not available in Terraform rancher2_cluster resource

Still relevant.

[RFE] useInstanceMetadataHostname not available in Terraform rancher2_cluster resource

Still relevant. On Wed, Feb 14, 2024, 03:46 github-actions[bot] ***@***.***> wrote: > This repository uses an automated workflow to automatically label issues > which have not had any activity (commit/comment/label)...

[RFE] useInstanceMetadataHostname not available in Terraform rancher2_cluster resource

Still relevant.