Currently I cannot find any docs about dependency-watchdog. Currently it seems to be:

1. probing the kube-apiserver and scaling down the kube-controller-manager to 0 replicas when the kube-apiserver is reachable internally but unreachable externally
2. restarting control plane components in CrashloopBackoff once etcd is again available

A gui for ssh-copy-id maybe?

and as the tittle says, support for ed25519 keys, maybe a dropdown menu that lets you choose the ehh... cipher is it? for generating a new one. Or at least the ability to connect using them.

Story
As a VIC developer I want an easy way to determine how a package functions and how it should be used.
As a VIC developer I want to easily see the call logic of code that I'm changing or reviewing

Details
We currently have a significant lack of good package documentation, at least in part because review inline doc is hard without generated output available. This documentation is

Just a small mistake in the README:

The README says:

See the Specifying Clusters and Hosts section above for more details.

But there is no such section above this line, there is only the "Working with Clusters" section below

Noticed that there is a folder argument for the vsphere_virtual_machine resource but not one for the equivalent data source. Instead, the name should be the full path of the template name.

This ticket is to update the documentation for this data source.

Affected Resource(s)

data source

• vsphere_virtual_machine

Terraform Configuration Files

data "vsphere_vir

Find a code coverage/review tool to run on every change and get it set up and running. Ideally, it would run all tests and report on the coverage as well as run RuboCop and potentially even more tools to ensure the code is only increasing in quality and never decreasing.

I struggled a bit yesterday and today, trying to land a VM on a standalong esxi host which was managed through vCenter. The value for --resource-pool was really tricky to nail.

The problem? My solo managed hosts are in a folder.

I'd love to write/see a mod to the docco around that command so when we run into that issue again, we won't have completely forgotten and get jammed up again.

Per Slack comment from @YanzhaoLi:

Could you help modify the vic doc: https://vmware.github.io/vic-product/assets/files/html/1.5/vic_vsphere_admin/vch_cert_options.html#auto-server ?
As customer says, we should point out that the server-crt.pem is self-signed, so that using the Server certificate for docker --tlscacert= which is the parameter referring to the CA certificate . I think we should

Error:
TASK [download : prep_kubeadm_images | Copy kubeadm binary from download dir to system path] ***
Thursday 02 January 2020 22:01:04 +0530 (0:00:00.778) 0:09:40.886 ******
fatal: [k8s-kubespray-master-0 -> 10.12.43.220]: FAILED! => {"changed": false, "cmd": "sshpass", "msg": "[Errno 2] No such file or directory: b'sshpass': b'sshpass'", "rc": 2}

Details:
Template Using : Ubuntu

/kind feature

Kubernetes has a providerless build tag which excludes all the in-tree cloud providers and their volume plugins. Even though the vSphere cloud provider works today with --cloud-provider=external set on all components, we should also validate that a pro

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind feature

What happened:
I am following the instructions provided at https://cloud-provider-vsphere.sigs.k8s.io/tutorials/kubernetes-on-vsphere-with-kubeadm.html in a new clean kubernetes v1.16.3 cluster runni

Prometheus best practices recommend how to name metrics. VMware's metric naming is different.

It would be nice to be able to expose metric according to those best practices.

The jmx_exporter has the same challenge of converting upstream metrics in Prometheus format so might be worth looking how they

• Create real world example for docker-compose
• Add hint: Project under heavy development: Data structures and configuration mechanisms are not fixed right now

When we create a VM as a fallback we should check the diskspace on a datastore/storage_pod before we commit and if there is not enough space left we fail and alert Foreman or the user if Foreman is not being used.

Improve the accessibility of ADLES to those who don't speak English or non-native speakers.

Tasks

• Identify areas that need to be localized
• Determine if there are any localization standards or guidelines we should adhere to
• Localize text in a portable manner (gettext and friends, as long as the database can be distributed with the package)
• Abide by system local

Feature Request

Detailed Description

the vcenter_ip variable will accept a DNS hostname, which seems like a more robust solution than hardcoding an ip address for the VCSA appliance. Neither the variable name or the documentation mention this.

https://bosh.io/docs/init-vsphere/

Configure vcenter_ip (e.g. '192.168.0.10') with the IP of the vCenter.

Context

CF Too

I have two forks right now, one that adds in Harbor and in Azure native Azure logging, then I have another using private DNS on Azure instead of public DNS (this will eventually be changed to use internal load balancers as well). Wondering how to provide these as easily referable and accessible to future users.