text:
Guide for disabling ipv6

Hi, I asked the question in irc of how to get the nic to stop assigning an ipv6 address to my machine.
My first attempted solution was to use the cloud config's write_files section and write /etc/netconfig with the ipv6 lines commented out,
write_files:
  - path: /etc/netconfig
    permissions: 0644
    owner: root
    content: |
      udp        tpi_clts      v     inet     udp     -       -
      tcp        tpi_cots_ord  v     inet     tcp     -       -
      #udp6       tpi_clts      v     inet6    udp     -       -
      #tcp6       tpi_cots_ord  v     inet6    tcp     -       -
      rawip      tpi_raw       -     inet      -      -       -
      local      tpi_cots_ord  -     loopback  -      -       -
      unix       tpi_cots_ord  -     loopback  -      -       -

however I was still getting an ipv6 address.
@philips gave an answer in a gist to write a file called 10-disable-ipv6.conf to /etc/sysctl.d/ with the content net.ipv6.conf.eth0.disable_ipv6 = 1
so the cloud-config (or user_data if already installed on bare metal) would look something like this:
write_files:
  - path: /etc/sysctl.d/10-disable-ipv6conf
    permissions: 0644
    owner: root
    content: |
      net.ipv6.conf.eth0.disable_ipv6 = 1

This issue is per request. He asked if I could file an issue so they could remember to document it.

What's the status of this? Does this need to be addressed in any documentation we currently have?

fwiw here's how i disable ipv6 on all interfaces:
core@ip-192-168-17-202 ~ $ cat /etc/sysctl.d/10-disable-ipv6.conf
net.ipv6.conf.all.disable_ipv6 = 1

# apply the config
core@ip-192-168-17-202 ~ $ sudo systemctl restart systemd-sysctl

# check addresses
core@ip-192-168-17-202 ~ $ ip -6 addr show
core@ip-192-168-17-202 ~ $ ip -4 addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9001 qdisc mq state UP group default qlen 1000
    inet 192.168.17.202/24 brd 192.168.17.255 scope global dynamic ens3
       valid_lft 3151sec preferred_lft 3151sec
3: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9001 qdisc noqueue state UP group default
    inet 172.17.42.1/16 scope global docker0
       valid_lft forever preferred_lft forever

I had to reboot my coreos vm after applying the changes through configdrive.iso.  The first boot seems to write the file, while the second boot respects the applied changes.
Also, I disabled IPv6 (aside from the fact that it's wholly unnecessary in a 40-employee shop) because this:
Aug 05 11:24:14 localhost systemd-resolved[495]: Detected conflict on localhost IN AAAA  2604:8800:100:81a0:250:56ff:fe3f:92a5
Aug 05 11:24:14 localhost systemd-resolved[495]: Hostname conflict, changing published hostname from 'localhost' to 'localhost3'.
Aug 05 11:24:14 localhost systemd-resolved[495]: Assertion 'e->key == i->next_key' failed at /build/amd64-usr/var/tmp/portage/sys-apps/systemd-220-r4/work/systemd-220/src/shared/ha

@gswallow to get it on first boot you can add:
coreos:
  units:
    - name: systemd-sysctl.service
      command: restart

#cloud-config

---
write_files:
- path: "/etc/sysctl.d/10-disable-ipv6conf"
  owner: root
  content: |
    net.ipv6.conf.all.disable_ipv6=1
coreos:
  units:
  - name: systemd-sysctl.service
    command: restart

The above cloud-config does not seem to make any difference. It does create the file, but no change to the kernel config.
Whereas when I run the sysctl command manually (as below) it does work.
sysctl net.ipv6.conf.eth0.disable_ipv6=1

Any idea why cloud config is not taking effect?

Peraphs you need a .conf in the filename under /etc/sysctl.d

Peraphs you need a .conf in the filename under /etc/sysctl.d

Yeah, that's probably it.
The combination of a .conf file containing the disables and a restart of sysctl works for us so far.
What net.ipv6.conf.all vs net.ipv6.conf.default does is a bit unclear, but judging by experiences from others it makes sense to disable both. See https://unix.stackexchange.com/questions/90443/sysctl-proc-sys-net-ipv46-conf-whats-the-difference-between-all-defau/90560#90560
write_files:
  - path: "/etc/sysctl.d/10-disable-ipv6.conf"
    owner: root
    content: |
      net.ipv6.conf.all.disable_ipv6=1
      net.ipv6.conf.default.disable_ipv6=1
coreos:
  units:
    - name: systemd-sysctl.service
      command: restart

I've encounter the same issue.
The ipv6 has been disabled by:
$ tail -3 /etc/default/grub
# disable ipv6
GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1"
GRUB_CMDLINE_LINUX="ipv6.disable=1"

$ sudo update-grub
$ sudo reboot

And for the ip a show:
$ ip -6 addr show

$ ip -4 addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: enp0s31f6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    inet 130.147.182.57/23 brd 130.147.183.255 scope global dynamic noprefixroute enp0s31f6
       valid_lft 690681sec preferred_lft 690681sec
3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    inet 192.168.10.235/23 brd 192.168.11.255 scope global dynamic noprefixroute wlp2s0
       valid_lft 85898sec preferred_lft 85898sec
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    inet 172.17.0.1/16 scope global docker0
       valid_lft forever preferred_lft forever
5: flannel.1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UNKNOWN group default
    inet 10.244.0.0/32 scope global flannel.1
       valid_lft forever preferred_lft forever

The pods status:
$ kubectl --namespace=kube-system get pods
NAME                                   READY     STATUS              RESTARTS   AGE
coredns-78fcdf6894-555tm               0/1       ContainerCreating   0          1h
coredns-78fcdf6894-c7lms               0/1       ContainerCreating   0          1h
etcd-imarslo18                         1/1       Running             1          1h
kube-apiserver-imarslo18               1/1       Running             1          1h
kube-controller-manager-imarslo18      1/1       Running             1          1h
kube-flannel-ds-f8j2z                  1/1       Running             1          56m
kube-proxy-sddp2                       1/1       Running             1          1h
kube-scheduler-imarslo18               1/1       Running             1          1h
kubernetes-dashboard-6948bdb78-hh8wm   0/1       ContainerCreating   0          19m

When I describe the pods:
$ kubectl --namespace=kube-system describe pods coredns-78fcdf6894-555tm
Name:           coredns-78fcdf6894-555tm
Namespace:      kube-system
Node:           imarslo18/192.168.10.235
Start Time:     Tue, 03 Jul 2018 18:49:20 +0800
Labels:         k8s-app=kube-dns
                pod-template-hash=3497892450
Annotations:    <none>
Status:         Pending
IP:
Controlled By:  ReplicaSet/coredns-78fcdf6894
Containers:
  coredns:
    Container ID:
    Image:         k8s.gcr.io/coredns:1.1.3
    Image ID:
    Ports:         53/UDP, 53/TCP, 9153/TCP
    Host Ports:    0/UDP, 0/TCP, 0/TCP
    Args:
      -conf
      /etc/coredns/Corefile
    State:          Waiting
      Reason:       ContainerCreating
    Ready:          False
    Restart Count:  0
    Limits:
      memory:  170Mi
    Requests:
      cpu:        100m
      memory:     70Mi
    Liveness:     http-get http://:8080/health delay=60s timeout=5s period=10s #success=1 #failure=5
    Environment:  <none>
    Mounts:
      /etc/coredns from config-volume (ro)
      /var/run/secrets/kubernetes.io/serviceaccount from coredns-token-k4xfp (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  config-volume:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      coredns
    Optional:  false
  coredns-token-k4xfp:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  coredns-token-k4xfp
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  <none>
Tolerations:     CriticalAddonsOnly
                 node-role.kubernetes.io/master:NoSchedule
                 node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason                  Age                  From                Message
  ----     ------                  ----                 ----                -------
  Warning  FailedScheduling        57m (x93 over 1h)    default-scheduler   0/1 nodes are available: 1 node(s) were not ready.
  Warning  FailedCreatePodSandBox  56m                  kubelet, imarslo18  Failed create pod sandbox: rpc error: code = Unknown desc = [failed to set up sandbox container "819e2f4395bfa32332180480b9d72a76c287154c19fd3a748f7cfb2acecc2af7" network for pod "coredns-78fcdf6894-555tm": NetworkPlugin cni failed to set up pod "coredns-78fcdf6894-555tm_kube-system" network: open /proc/sys/net/ipv6/conf/eth0/accept_dad: no such file or directory, failed to clean up sandbox container "819e2f4395bfa32332180480b9d72a76c287154c19fd3a748f7cfb2acecc2af7" network for pod "coredns-78fcdf6894-555tm": NetworkPlugin cni failed to teardown pod "coredns-78fcdf6894-555tm_kube-system" network: failed to get IP addresses for "eth0": <nil>]

The error shows it's looking for the open /proc/sys/net/ipv6/conf/eth0/accept_dad: no such file or directory
My system details:
$ kubeadm version
kubeadm version: &version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.0", GitCommit:"91e7b4fd31fcd3d5f436da26c980becec37ceefe", GitTreeState:"clean", BuildDate:"2018-06-27T20:14:41Z", GoVersion:"go1.10.2", Compiler:"gc", Platform:"linux/amd64"}

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.0", GitCommit:"91e7b4fd31fcd3d5f436da26c980becec37ceefe", GitTreeState:"clean", BuildDate:"2018-06-27T20:17:28Z", GoVersion:"go1.10.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.0", GitCommit:"91e7b4fd31fcd3d5f436da26c980becec37ceefe", GitTreeState:"clean", BuildDate:"2018-06-27T20:08:34Z", GoVersion:"go1.10.2", Compiler:"gc", Platform:"linux/amd64"}

$ cat /etc/sysctl.conf
net.ipv4.ip_forward=1
net.bridge.bridge-nf-call-iptables=1
net.bridge.bridge-nf-call-ip6tables=1
net.ipv6.conf.all.forwarding=0
net.ipv6.conf.all.disable_ipv6=1
net.ipv6.conf.default.disable_ipv6=1
net.ipv6.conf.lo.disable_ipv6=1

$ sudo sysctl -p
net.ipv4.ip_forward = 1
net.bridge.bridge-nf-call-iptables = 1
net.bridge.bridge-nf-call-ip6tables = 1
sysctl: cannot stat /proc/sys/net/ipv6/conf/all/forwarding: No such file or directory
sysctl: cannot stat /proc/sys/net/ipv6/conf/all/disable_ipv6: No such file or directory
sysctl: cannot stat /proc/sys/net/ipv6/conf/default/disable_ipv6: No such file or directory
sysctl: cannot stat /proc/sys/net/ipv6/conf/lo/disable_ipv6: No such file or directory

@Marslo that looks like a CNI bug, please report it there.

You are using an old version of CNI, which does not work on systems with ipv6 disabled. Please re-enable ipv6 or upgrade CNI.

@squeed , the kubernetes master is init this afternoon. And the the init command as blow. I don't think this should be the old version CNI. I will submit the error to CNI.
$ sudo kubeadm init --ignore-preflight-errors=all --pod-network-cidr=10.244.0.0/16 --apiserver-advertise-address=130.147.182.57 --kubernetes-version=v1.11.0
I0703 18:29:14.713462    6850 feature_gate.go:230] feature gates: &{map[]}
[init] using Kubernetes version: v1.11.0
[preflight] running pre-flight checks
I0703 18:29:14.814406    6850 kernel_validator.go:81] Validating kernel version
I0703 18:29:14.814547    6850 kernel_validator.go:96] Validating kernel config
[preflight/images] Pulling images required for setting up a Kubernetes cluster
[preflight/images] This might take a minute or two, depending on the speed of your internet connection
[preflight/images] You can also perform this action in beforehand using 'kubeadm config images pull'
[kubelet] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[preflight] Activating the kubelet service
[certificates] Generated ca certificate and key.
[certificates] Generated apiserver certificate and key.
[certificates] apiserver serving cert is signed for DNS names [imarslo18 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 130.147.182.57]
[certificates] Generated apiserver-kubelet-client certificate and key.
[certificates] Generated sa key and public key.
[certificates] Generated front-proxy-ca certificate and key.
[certificates] Generated front-proxy-client certificate and key.
[certificates] Generated etcd/ca certificate and key.
[certificates] Generated etcd/server certificate and key.
[certificates] etcd/server serving cert is signed for DNS names [imarslo18 localhost] and IPs [127.0.0.1 ::1]
[certificates] Generated etcd/peer certificate and key.
[certificates] etcd/peer serving cert is signed for DNS names [imarslo18 localhost] and IPs [130.147.182.57 127.0.0.1 ::1]
[certificates] Generated etcd/healthcheck-client certificate and key.
[certificates] Generated apiserver-etcd-client certificate and key.
[certificates] valid certificates and keys now exist in "/etc/kubernetes/pki"
[kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/admin.conf"
[kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/kubelet.conf"
[kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/controller-manager.conf"
[kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/scheduler.conf"
[controlplane] wrote Static Pod manifest for component kube-apiserver to "/etc/kubernetes/manifests/kube-apiserver.yaml"
[controlplane] wrote Static Pod manifest for component kube-controller-manager to "/etc/kubernetes/manifests/kube-controller-manager.yaml"
[controlplane] wrote Static Pod manifest for component kube-scheduler to "/etc/kubernetes/manifests/kube-scheduler.yaml"
[etcd] Wrote Static Pod manifest for a local etcd instance to "/etc/kubernetes/manifests/etcd.yaml"
[init] waiting for the kubelet to boot up the control plane as Static Pods from directory "/etc/kubernetes/manifests"
[init] this might take a minute or longer if the control plane images have to be pulled
[apiclient] All control plane components are healthy after 60.503799 seconds
[uploadconfig] storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
[kubelet] Creating a ConfigMap "kubelet-config-1.11" in namespace kube-system with the configuration for the kubelets in the cluster
[markmaster] Marking the node imarslo18 as master by adding the label "node-role.kubernetes.io/master=''"
[markmaster] Marking the node imarslo18 as master by adding the taints [node-role.kubernetes.io/master:NoSchedule]
[patchnode] Uploading the CRI Socket information "/var/run/dockershim.sock" to the Node API object "imarslo18" as an annotation
[bootstraptoken] using token: 5yks9y.r8tr98s2bd1fqgiz
[bootstraptoken] configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials
[bootstraptoken] configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token
[bootstraptoken] configured RBAC rules to allow certificate rotation for all node client certificates in the cluster
[bootstraptoken] creating the "cluster-info" ConfigMap in the "kube-public" namespace
[addons] Applied essential addon: CoreDNS
[addons] Applied essential addon: kube-proxy

Your Kubernetes master has initialized successfully!
....
....

authors: Marslo codemedic gswallow jumanjiman lucab mimmus robszumski schneidexe simonvanderveldt squeed treehau5

repo: coreos/docs


text:
etcd print warning logs even there's only 1 member in the cluster

The cluster single member cluster. So there shouldn't be any reason that print the large range operations.
2016-12-29 07:52:35.010920 W | etcdserver: apply entries took too long [11.13718ms for 1 entries]
2016-12-29 07:52:35.010967 W | etcdserver: avoid queries with large range/delete range!
2016-12-29 07:52:39.799901 W | etcdserver: apply entries took too long [17.108421ms for 1 entries]
2016-12-29 07:52:39.799948 W | etcdserver: avoid queries with large range/delete range!

Could SSL be the root cause? or the slow disk could be ?
Here is the metrics
bash-4.3# curl -k https://localhost:4001/metrics
# HELP etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds Bucketed histogram of db compaction pause duration.
# TYPE etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds histogram
etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="1"} 0
etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="2"} 0
etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="4"} 0
etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="8"} 0
etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="16"} 0
etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="32"} 0
etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="64"} 0
etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="128"} 0
etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="256"} 0
etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="512"} 0
etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="1024"} 0
etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="2048"} 0
etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="4096"} 0
etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_bucket{le="+Inf"} 0
etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_sum 0
etcd_debugging_mvcc_db_compaction_pause_duration_milliseconds_count 0
# HELP etcd_debugging_mvcc_db_compaction_total_duration_milliseconds Bucketed histogram of db compaction total duration.
# TYPE etcd_debugging_mvcc_db_compaction_total_duration_milliseconds histogram
etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="100"} 0
etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="200"} 0
etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="400"} 0
etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="800"} 0
etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="1600"} 0
etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="3200"} 0
etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="6400"} 0
etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="12800"} 0
etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="25600"} 0
etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="51200"} 0
etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="102400"} 0
etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="204800"} 0
etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="409600"} 0
etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="819200"} 0
etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_bucket{le="+Inf"} 0
etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_sum 0
etcd_debugging_mvcc_db_compaction_total_duration_milliseconds_count 0
# HELP etcd_debugging_mvcc_db_total_size_in_bytes Total size of the underlying database in bytes.
# TYPE etcd_debugging_mvcc_db_total_size_in_bytes gauge
etcd_debugging_mvcc_db_total_size_in_bytes 0
# HELP etcd_debugging_mvcc_delete_total Total number of deletes seen by this member.
# TYPE etcd_debugging_mvcc_delete_total counter
etcd_debugging_mvcc_delete_total 0
# HELP etcd_debugging_mvcc_events_total Total number of events sent by this member.
# TYPE etcd_debugging_mvcc_events_total counter
etcd_debugging_mvcc_events_total 0
# HELP etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds Bucketed histogram of index compaction pause duration.
# TYPE etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds histogram
etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="0.5"} 0
etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="1"} 0
etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="2"} 0
etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="4"} 0
etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="8"} 0
etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="16"} 0
etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="32"} 0
etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="64"} 0
etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="128"} 0
etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="256"} 0
etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="512"} 0
etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="1024"} 0
etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_bucket{le="+Inf"} 0
etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_sum 0
etcd_debugging_mvcc_index_compaction_pause_duration_milliseconds_count 0
# HELP etcd_debugging_mvcc_keys_total Total number of keys.
# TYPE etcd_debugging_mvcc_keys_total gauge
etcd_debugging_mvcc_keys_total 0
# HELP etcd_debugging_mvcc_pending_events_total Total number of pending events to be sent.
# TYPE etcd_debugging_mvcc_pending_events_total gauge
etcd_debugging_mvcc_pending_events_total 0
# HELP etcd_debugging_mvcc_put_total Total number of puts seen by this member.
# TYPE etcd_debugging_mvcc_put_total counter
etcd_debugging_mvcc_put_total 0
# HELP etcd_debugging_mvcc_range_total Total number of ranges seen by this member.
# TYPE etcd_debugging_mvcc_range_total counter
etcd_debugging_mvcc_range_total 0
# HELP etcd_debugging_mvcc_slow_watcher_total Total number of unsynced slow watchers.
# TYPE etcd_debugging_mvcc_slow_watcher_total gauge
etcd_debugging_mvcc_slow_watcher_total 0
# HELP etcd_debugging_mvcc_txn_total Total number of txns seen by this member.
# TYPE etcd_debugging_mvcc_txn_total counter
etcd_debugging_mvcc_txn_total 0
# HELP etcd_debugging_mvcc_watch_stream_total Total number of watch streams.
# TYPE etcd_debugging_mvcc_watch_stream_total gauge
etcd_debugging_mvcc_watch_stream_total 0
# HELP etcd_debugging_mvcc_watcher_total Total number of watchers.
# TYPE etcd_debugging_mvcc_watcher_total gauge
etcd_debugging_mvcc_watcher_total 0
# HELP etcd_debugging_snap_save_marshalling_duration_seconds The marshalling cost distributions of save called by snapshot.
# TYPE etcd_debugging_snap_save_marshalling_duration_seconds histogram
etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.001"} 0
etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.002"} 0
etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.004"} 0
etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.008"} 0
etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.016"} 0
etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.032"} 0
etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.064"} 0
etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.128"} 0
etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.256"} 0
etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="0.512"} 0
etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="1.024"} 0
etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="2.048"} 0
etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="4.096"} 0
etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="8.192"} 0
etcd_debugging_snap_save_marshalling_duration_seconds_bucket{le="+Inf"} 0
etcd_debugging_snap_save_marshalling_duration_seconds_sum 0
etcd_debugging_snap_save_marshalling_duration_seconds_count 0
# HELP etcd_debugging_snap_save_total_duration_seconds The total latency distributions of save called by snapshot.
# TYPE etcd_debugging_snap_save_total_duration_seconds histogram
etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.001"} 0
etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.002"} 0
etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.004"} 0
etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.008"} 0
etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.016"} 0
etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.032"} 0
etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.064"} 0
etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.128"} 0
etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.256"} 0
etcd_debugging_snap_save_total_duration_seconds_bucket{le="0.512"} 0
etcd_debugging_snap_save_total_duration_seconds_bucket{le="1.024"} 0
etcd_debugging_snap_save_total_duration_seconds_bucket{le="2.048"} 0
etcd_debugging_snap_save_total_duration_seconds_bucket{le="4.096"} 0
etcd_debugging_snap_save_total_duration_seconds_bucket{le="8.192"} 0
etcd_debugging_snap_save_total_duration_seconds_bucket{le="+Inf"} 0
etcd_debugging_snap_save_total_duration_seconds_sum 0
etcd_debugging_snap_save_total_duration_seconds_count 0
# HELP etcd_debugging_store_expires_total Total number of expired keys.
# TYPE etcd_debugging_store_expires_total counter
etcd_debugging_store_expires_total 0
# HELP etcd_debugging_store_reads_total Total number of reads action by (get/getRecursive), local to this member.
# TYPE etcd_debugging_store_reads_total counter
etcd_debugging_store_reads_total{action="get"} 32445
etcd_debugging_store_reads_total{action="getRecursive"} 5045
# HELP etcd_debugging_store_watch_requests_total Total number of incoming watch requests (new or reestablished).
# TYPE etcd_debugging_store_watch_requests_total counter
etcd_debugging_store_watch_requests_total 1040
# HELP etcd_debugging_store_watchers Count of currently active watchers.
# TYPE etcd_debugging_store_watchers gauge
etcd_debugging_store_watchers 44
# HELP etcd_debugging_store_writes_total Total number of writes (e.g. set/compareAndDelete) seen by this member.
# TYPE etcd_debugging_store_writes_total counter
etcd_debugging_store_writes_total{action="compareAndSwap"} 753
etcd_debugging_store_writes_total{action="create"} 451
etcd_debugging_store_writes_total{action="set"} 2
# HELP etcd_disk_backend_commit_duration_seconds The latency distributions of commit called by backend.
# TYPE etcd_disk_backend_commit_duration_seconds histogram
etcd_disk_backend_commit_duration_seconds_bucket{le="0.001"} 4
etcd_disk_backend_commit_duration_seconds_bucket{le="0.002"} 6
etcd_disk_backend_commit_duration_seconds_bucket{le="0.004"} 7
etcd_disk_backend_commit_duration_seconds_bucket{le="0.008"} 7
etcd_disk_backend_commit_duration_seconds_bucket{le="0.016"} 7
etcd_disk_backend_commit_duration_seconds_bucket{le="0.032"} 7
etcd_disk_backend_commit_duration_seconds_bucket{le="0.064"} 7
etcd_disk_backend_commit_duration_seconds_bucket{le="0.128"} 7
etcd_disk_backend_commit_duration_seconds_bucket{le="0.256"} 7
etcd_disk_backend_commit_duration_seconds_bucket{le="0.512"} 7
etcd_disk_backend_commit_duration_seconds_bucket{le="1.024"} 7
etcd_disk_backend_commit_duration_seconds_bucket{le="2.048"} 7
etcd_disk_backend_commit_duration_seconds_bucket{le="4.096"} 7
etcd_disk_backend_commit_duration_seconds_bucket{le="8.192"} 7
etcd_disk_backend_commit_duration_seconds_bucket{le="+Inf"} 7
etcd_disk_backend_commit_duration_seconds_sum 0.008199347000000001
etcd_disk_backend_commit_duration_seconds_count 7
# HELP etcd_disk_wal_fsync_duration_seconds The latency distributions of fsync called by wal.
# TYPE etcd_disk_wal_fsync_duration_seconds histogram
etcd_disk_wal_fsync_duration_seconds_bucket{le="0.001"} 1182
etcd_disk_wal_fsync_duration_seconds_bucket{le="0.002"} 1504
etcd_disk_wal_fsync_duration_seconds_bucket{le="0.004"} 1591
etcd_disk_wal_fsync_duration_seconds_bucket{le="0.008"} 1621
etcd_disk_wal_fsync_duration_seconds_bucket{le="0.016"} 1662
etcd_disk_wal_fsync_duration_seconds_bucket{le="0.032"} 1701
etcd_disk_wal_fsync_duration_seconds_bucket{le="0.064"} 1709
etcd_disk_wal_fsync_duration_seconds_bucket{le="0.128"} 1710
etcd_disk_wal_fsync_duration_seconds_bucket{le="0.256"} 1710
etcd_disk_wal_fsync_duration_seconds_bucket{le="0.512"} 1711
etcd_disk_wal_fsync_duration_seconds_bucket{le="1.024"} 1711
etcd_disk_wal_fsync_duration_seconds_bucket{le="2.048"} 1711
etcd_disk_wal_fsync_duration_seconds_bucket{le="4.096"} 1711
etcd_disk_wal_fsync_duration_seconds_bucket{le="8.192"} 1711
etcd_disk_wal_fsync_duration_seconds_bucket{le="+Inf"} 1711
etcd_disk_wal_fsync_duration_seconds_sum 3.666582928000004
etcd_disk_wal_fsync_duration_seconds_count 1711
# HELP etcd_http_failed_total Counter of handle failures of requests (non-watches), by method (GET/PUT etc.) and code (400, 500 etc.).
# TYPE etcd_http_failed_total counter
etcd_http_failed_total{code="404",method="GET"} 1821
etcd_http_failed_total{code="412",method="PUT"} 31
# HELP etcd_http_received_total Counter of requests received into the system (successfully parsed and authd).
# TYPE etcd_http_received_total counter
etcd_http_received_total{method="GET"} 17623
etcd_http_received_total{method="PUT"} 1203
# HELP etcd_http_successful_duration_seconds Bucketed histogram of processing time (s) of successfully handled requests (non-watches), by method (GET/PUT etc.).
# TYPE etcd_http_successful_duration_seconds histogram
etcd_http_successful_duration_seconds_bucket{method="GET",le="0.0005"} 15683
etcd_http_successful_duration_seconds_bucket{method="GET",le="0.001"} 15720
etcd_http_successful_duration_seconds_bucket{method="GET",le="0.002"} 15762
etcd_http_successful_duration_seconds_bucket{method="GET",le="0.004"} 15787
etcd_http_successful_duration_seconds_bucket{method="GET",le="0.008"} 15797
etcd_http_successful_duration_seconds_bucket{method="GET",le="0.016"} 15802
etcd_http_successful_duration_seconds_bucket{method="GET",le="0.032"} 15802
etcd_http_successful_duration_seconds_bucket{method="GET",le="0.064"} 15802
etcd_http_successful_duration_seconds_bucket{method="GET",le="0.128"} 15802
etcd_http_successful_duration_seconds_bucket{method="GET",le="0.256"} 15802
etcd_http_successful_duration_seconds_bucket{method="GET",le="0.512"} 15802
etcd_http_successful_duration_seconds_bucket{method="GET",le="1.024"} 15802
etcd_http_successful_duration_seconds_bucket{method="GET",le="2.048"} 15802
etcd_http_successful_duration_seconds_bucket{method="GET",le="+Inf"} 15802
etcd_http_successful_duration_seconds_sum{method="GET"} 1.5607077459999963
etcd_http_successful_duration_seconds_count{method="GET"} 15802
etcd_http_successful_duration_seconds_bucket{method="PUT",le="0.0005"} 720
etcd_http_successful_duration_seconds_bucket{method="PUT",le="0.001"} 1017
etcd_http_successful_duration_seconds_bucket{method="PUT",le="0.002"} 1084
etcd_http_successful_duration_seconds_bucket{method="PUT",le="0.004"} 1122
etcd_http_successful_duration_seconds_bucket{method="PUT",le="0.008"} 1147
etcd_http_successful_duration_seconds_bucket{method="PUT",le="0.016"} 1161
etcd_http_successful_duration_seconds_bucket{method="PUT",le="0.032"} 1163
etcd_http_successful_duration_seconds_bucket{method="PUT",le="0.064"} 1168
etcd_http_successful_duration_seconds_bucket{method="PUT",le="0.128"} 1170
etcd_http_successful_duration_seconds_bucket{method="PUT",le="0.256"} 1172
etcd_http_successful_duration_seconds_bucket{method="PUT",le="0.512"} 1172
etcd_http_successful_duration_seconds_bucket{method="PUT",le="1.024"} 1172
etcd_http_successful_duration_seconds_bucket{method="PUT",le="2.048"} 1172
etcd_http_successful_duration_seconds_bucket{method="PUT",le="+Inf"} 1172
etcd_http_successful_duration_seconds_sum{method="PUT"} 1.7888432390000018
etcd_http_successful_duration_seconds_count{method="PUT"} 1172
# HELP etcd_network_client_grpc_received_bytes_total The total number of bytes received from grpc clients.
# TYPE etcd_network_client_grpc_received_bytes_total counter
etcd_network_client_grpc_received_bytes_total 0
# HELP etcd_network_client_grpc_sent_bytes_total The total number of bytes sent to grpc clients.
# TYPE etcd_network_client_grpc_sent_bytes_total counter
etcd_network_client_grpc_sent_bytes_total 0
# HELP etcd_server_has_leader Whether or not a leader exists. 1 is existence, 0 is not.
# TYPE etcd_server_has_leader gauge
etcd_server_has_leader 1
# HELP etcd_server_leader_changes_seen_total The number of leader changes seen.
# TYPE etcd_server_leader_changes_seen_total counter
etcd_server_leader_changes_seen_total 1
# HELP etcd_server_proposals_applied_total The total number of consensus proposals applied.
# TYPE etcd_server_proposals_applied_total gauge
etcd_server_proposals_applied_total 1744
# HELP etcd_server_proposals_committed_total The total number of consensus proposals committed.
# TYPE etcd_server_proposals_committed_total gauge
etcd_server_proposals_committed_total 1744
# HELP etcd_server_proposals_failed_total The total number of failed proposals seen.
# TYPE etcd_server_proposals_failed_total gauge
etcd_server_proposals_failed_total 0
# HELP etcd_server_proposals_pending The current number of pending proposals to commit.
# TYPE etcd_server_proposals_pending gauge
etcd_server_proposals_pending 0
# HELP go_gc_duration_seconds A summary of the GC invocation durations.
# TYPE go_gc_duration_seconds summary
go_gc_duration_seconds{quantile="0"} 0.000171349
go_gc_duration_seconds{quantile="0.25"} 0.00044754500000000004
go_gc_duration_seconds{quantile="0.5"} 0.00087323
go_gc_duration_seconds{quantile="0.75"} 0.0020569850000000003
go_gc_duration_seconds{quantile="1"} 0.018553187000000002
go_gc_duration_seconds_sum 0.11964173300000001
go_gc_duration_seconds_count 49
# HELP go_goroutines Number of goroutines that currently exist.
# TYPE go_goroutines gauge
go_goroutines 270
# HELP go_memstats_alloc_bytes Number of bytes allocated and still in use.
# TYPE go_memstats_alloc_bytes gauge
go_memstats_alloc_bytes 1.3064672e+07
# HELP go_memstats_alloc_bytes_total Total number of bytes allocated, even if freed.
# TYPE go_memstats_alloc_bytes_total counter
go_memstats_alloc_bytes_total 2.48836232e+08
# HELP go_memstats_buck_hash_sys_bytes Number of bytes used by the profiling bucket hash table.
# TYPE go_memstats_buck_hash_sys_bytes gauge
go_memstats_buck_hash_sys_bytes 1.490512e+06
# HELP go_memstats_frees_total Total number of frees.
# TYPE go_memstats_frees_total counter
go_memstats_frees_total 2.981695e+06
# HELP go_memstats_gc_sys_bytes Number of bytes used for garbage collection system metadata.
# TYPE go_memstats_gc_sys_bytes gauge
go_memstats_gc_sys_bytes 768000
# HELP go_memstats_heap_alloc_bytes Number of heap bytes allocated and still in use.
# TYPE go_memstats_heap_alloc_bytes gauge
go_memstats_heap_alloc_bytes 1.3064672e+07
# HELP go_memstats_heap_idle_bytes Number of heap bytes waiting to be used.
# TYPE go_memstats_heap_idle_bytes gauge
go_memstats_heap_idle_bytes 2.441216e+06
# HELP go_memstats_heap_inuse_bytes Number of heap bytes that are in use.
# TYPE go_memstats_heap_inuse_bytes gauge
go_memstats_heap_inuse_bytes 1.8038784e+07
# HELP go_memstats_heap_objects Number of allocated objects.
# TYPE go_memstats_heap_objects gauge
go_memstats_heap_objects 76686
# HELP go_memstats_heap_released_bytes_total Total number of heap bytes released to OS.
# TYPE go_memstats_heap_released_bytes_total counter
go_memstats_heap_released_bytes_total 0
# HELP go_memstats_heap_sys_bytes Number of heap bytes obtained from system.
# TYPE go_memstats_heap_sys_bytes gauge
go_memstats_heap_sys_bytes 2.048e+07
# HELP go_memstats_last_gc_time_seconds Number of seconds since 1970 of last garbage collection.
# TYPE go_memstats_last_gc_time_seconds gauge
go_memstats_last_gc_time_seconds 1.4829981936423948e+19
# HELP go_memstats_lookups_total Total number of pointer lookups.
# TYPE go_memstats_lookups_total counter
go_memstats_lookups_total 368
# HELP go_memstats_mallocs_total Total number of mallocs.
# TYPE go_memstats_mallocs_total counter
go_memstats_mallocs_total 3.058381e+06
# HELP go_memstats_mcache_inuse_bytes Number of bytes in use by mcache structures.
# TYPE go_memstats_mcache_inuse_bytes gauge
go_memstats_mcache_inuse_bytes 4800
# HELP go_memstats_mcache_sys_bytes Number of bytes used for mcache structures obtained from system.
# TYPE go_memstats_mcache_sys_bytes gauge
go_memstats_mcache_sys_bytes 16384
# HELP go_memstats_mspan_inuse_bytes Number of bytes in use by mspan structures.
# TYPE go_memstats_mspan_inuse_bytes gauge
go_memstats_mspan_inuse_bytes 235440
# HELP go_memstats_mspan_sys_bytes Number of bytes used for mspan structures obtained from system.
# TYPE go_memstats_mspan_sys_bytes gauge
go_memstats_mspan_sys_bytes 262144
# HELP go_memstats_next_gc_bytes Number of heap bytes when next garbage collection will take place.
# TYPE go_memstats_next_gc_bytes gauge
go_memstats_next_gc_bytes 1.8728704e+07
# HELP go_memstats_other_sys_bytes Number of bytes used for other system allocations.
# TYPE go_memstats_other_sys_bytes gauge
go_memstats_other_sys_bytes 1.02468e+06
# HELP go_memstats_stack_inuse_bytes Number of bytes in use by the stack allocator.
# TYPE go_memstats_stack_inuse_bytes gauge
go_memstats_stack_inuse_bytes 2.588672e+06
# HELP go_memstats_stack_sys_bytes Number of bytes obtained from system for stack allocator.
# TYPE go_memstats_stack_sys_bytes gauge
go_memstats_stack_sys_bytes 2.588672e+06
# HELP go_memstats_sys_bytes Number of bytes obtained by system. Sum of all system allocations.
# TYPE go_memstats_sys_bytes gauge
go_memstats_sys_bytes 2.6630392e+07
# HELP http_request_duration_microseconds The HTTP request latencies in microseconds.
# TYPE http_request_duration_microseconds summary
http_request_duration_microseconds{handler="prometheus",quantile="0.5"} NaN
http_request_duration_microseconds{handler="prometheus",quantile="0.9"} NaN
http_request_duration_microseconds{handler="prometheus",quantile="0.99"} NaN
http_request_duration_microseconds_sum{handler="prometheus"} 0
http_request_duration_microseconds_count{handler="prometheus"} 0
# HELP http_request_size_bytes The HTTP request sizes in bytes.
# TYPE http_request_size_bytes summary
http_request_size_bytes{handler="prometheus",quantile="0.5"} NaN
http_request_size_bytes{handler="prometheus",quantile="0.9"} NaN
http_request_size_bytes{handler="prometheus",quantile="0.99"} NaN
http_request_size_bytes_sum{handler="prometheus"} 0
http_request_size_bytes_count{handler="prometheus"} 0
# HELP http_response_size_bytes The HTTP response sizes in bytes.
# TYPE http_response_size_bytes summary
http_response_size_bytes{handler="prometheus",quantile="0.5"} NaN
http_response_size_bytes{handler="prometheus",quantile="0.9"} NaN
http_response_size_bytes{handler="prometheus",quantile="0.99"} NaN
http_response_size_bytes_sum{handler="prometheus"} 0
http_response_size_bytes_count{handler="prometheus"} 0
# HELP process_cpu_seconds_total Total user and system CPU time spent in seconds.
# TYPE process_cpu_seconds_total counter
process_cpu_seconds_total 7.7
# HELP process_max_fds Maximum number of open file descriptors.
# TYPE process_max_fds gauge
process_max_fds 1.048576e+06
# HELP process_open_fds Number of open file descriptors.
# TYPE process_open_fds gauge
process_open_fds 176
# HELP process_resident_memory_bytes Resident memory size in bytes.
# TYPE process_resident_memory_bytes gauge
process_resident_memory_bytes 3.6016128e+07
# HELP process_start_time_seconds Start time of the process since unix epoch in seconds.
# TYPE process_start_time_seconds gauge
process_start_time_seconds 1.48299793838e+09
# HELP process_virtual_memory_bytes Virtual memory size in bytes.
# TYPE process_virtual_memory_bytes gauge
process_virtual_memory_bytes 1.0784571392e+10

Everything is fine. We set the warning limit too tight in 3.0. It has been fixed in master.

source: gharchive/issue

repo: coreos/etcd

license_type: permissive

license_source: github-api


text:
clientv3/integration: Get with context timeout

Address https://github.com/coreos/etcd/pull/8762#discussion_r147019068.

lgtm

source: gharchive/pull-request


text:
[ support ] not working but I don't know why

What did you do?
from The Prometheus Operator: Managed Prometheus setups for Kubernetes to deploy prometheus in k8s cluster, but failed when deploy prometheus resouce
What did you expect to see?
success
What did you see instead? Under which circumstances?
$ kubectl apply -f prometheus.yaml
service "prometheus-k8s" configured
error: unable to recognize "prometheus.yaml": no matches for kind "Prometheus" in version "monitoring.coreos.com/v1alpha1"

Environment

Kubernetes version information:

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.1", GitCommit:"d4ab47518836c750f9949b9e0d387f20fb92260b", GitTreeState:"clean", BuildDate:"2018-04-12T14:26:04Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.1", GitCommit:"d4ab47518836c750f9949b9e0d387f20fb92260b", GitTreeState:"clean", BuildDate:"2018-04-12T14:14:26Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes cluster kind:

use kubeadm to install k8s cluster.

Manifests:

# cat etcd.yaml
apiVersion: v1
kind: Pod
metadata:
  annotations:
    scheduler.alpha.kubernetes.io/critical-pod: ""
  creationTimestamp: null
  labels:
    component: etcd
    tier: control-plane
  name: etcd
  namespace: kube-system
spec:
  containers:
  - command:
    - etcd
    - --peer-cert-file=/etc/kubernetes/pki/etcd/peer.crt
    - --peer-key-file=/etc/kubernetes/pki/etcd/peer.key
    - --advertise-client-urls=https://127.0.0.1:2379
    - --client-cert-auth=true
    - --peer-client-cert-auth=true
    - --key-file=/etc/kubernetes/pki/etcd/server.key
    - --trusted-ca-file=/etc/kubernetes/pki/etcd/ca.crt
    - --peer-trusted-ca-file=/etc/kubernetes/pki/etcd/ca.crt
    - --listen-client-urls=https://127.0.0.1:2379
    - --data-dir=/var/lib/etcd
    - --cert-file=/etc/kubernetes/pki/etcd/server.crt
    image: k8s.gcr.io/etcd-amd64:3.1.12
    livenessProbe:
      exec:
        command:
        - /bin/sh
        - -ec
        - ETCDCTL_API=3 etcdctl --endpoints=127.0.0.1:2379 --cacert=/etc/kubernetes/pki/etcd/ca.crt
          --cert=/etc/kubernetes/pki/etcd/healthcheck-client.crt --key=/etc/kubernetes/pki/etcd/healthcheck-client.key
          get foo
      failureThreshold: 8
      initialDelaySeconds: 15
      timeoutSeconds: 15
    name: etcd
    resources: {}
    volumeMounts:
    - mountPath: /var/lib/etcd
      name: etcd-data
    - mountPath: /etc/kubernetes/pki/etcd
      name: etcd-certs
  hostNetwork: true
  volumes:
  - hostPath:
      path: /var/lib/etcd
      type: DirectoryOrCreate
    name: etcd-data
  - hostPath:
      path: /etc/kubernetes/pki/etcd
      type: DirectoryOrCreate
    name: etcd-certs
status: {}

# cat kube-apiserver.yaml
apiVersion: v1
kind: Pod
metadata:
  annotations:
    scheduler.alpha.kubernetes.io/critical-pod: ""
  creationTimestamp: null
  labels:
    component: kube-apiserver
    tier: control-plane
  name: kube-apiserver
  namespace: kube-system
spec:
  containers:
  - command:
    - kube-apiserver
    - --tls-cert-file=/etc/kubernetes/pki/apiserver.crt
    - --kubelet-client-certificate=/etc/kubernetes/pki/apiserver-kubelet-client.crt
    - --kubelet-client-key=/etc/kubernetes/pki/apiserver-kubelet-client.key
    - --insecure-port=0
    - --enable-bootstrap-token-auth=true
    - --requestheader-group-headers=X-Remote-Group
    - --requestheader-extra-headers-prefix=X-Remote-Extra-
    - --allow-privileged=true
    - --requestheader-allowed-names=front-proxy-client
    - --tls-private-key-file=/etc/kubernetes/pki/apiserver.key
    - --secure-port=6443
    - --client-ca-file=/etc/kubernetes/pki/ca.crt
    - --proxy-client-cert-file=/etc/kubernetes/pki/front-proxy-client.crt
    - --admission-control=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,NodeRestriction,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota
    - --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname
    - --service-cluster-ip-range=10.96.0.0/12
    - --service-account-key-file=/etc/kubernetes/pki/sa.pub
    - --requestheader-username-headers=X-Remote-User
    - --advertise-address=192.168.64.128
    - --requestheader-client-ca-file=/etc/kubernetes/pki/front-proxy-ca.crt
    - --proxy-client-key-file=/etc/kubernetes/pki/front-proxy-client.key
    - --authorization-mode=Node,RBAC
    - --etcd-servers=https://127.0.0.1:2379
    - --etcd-cafile=/etc/kubernetes/pki/etcd/ca.crt
    - --etcd-certfile=/etc/kubernetes/pki/apiserver-etcd-client.crt
    - --etcd-keyfile=/etc/kubernetes/pki/apiserver-etcd-client.key
    image: k8s.gcr.io/kube-apiserver-amd64:v1.10.1
    livenessProbe:
      failureThreshold: 8
      httpGet:
        host: 192.168.64.128
        path: /healthz
        port: 6443
        scheme: HTTPS
      initialDelaySeconds: 15
      timeoutSeconds: 15
    name: kube-apiserver
    resources:
      requests:
        cpu: 250m
    volumeMounts:
    - mountPath: /etc/kubernetes/pki
      name: k8s-certs
      readOnly: true
    - mountPath: /etc/ssl/certs
      name: ca-certs
      readOnly: true
  hostNetwork: true
  volumes:
  - hostPath:
      path: /etc/kubernetes/pki
      type: DirectoryOrCreate
    name: k8s-certs
  - hostPath:
      path: /etc/ssl/certs
      type: DirectoryOrCreate
    name: ca-certs
status: {}

# cat kube-controller-manager.yaml
apiVersion: v1
kind: Pod
metadata:
  annotations:
    scheduler.alpha.kubernetes.io/critical-pod: ""
  creationTimestamp: null
  labels:
    component: kube-controller-manager
    tier: control-plane
  name: kube-controller-manager
  namespace: kube-system
spec:
  containers:
  - command:
    - kube-controller-manager
    - --service-account-private-key-file=/etc/kubernetes/pki/sa.key
    - --cluster-signing-cert-file=/etc/kubernetes/pki/ca.crt
    - --controllers=*,bootstrapsigner,tokencleaner
    - --kubeconfig=/etc/kubernetes/controller-manager.conf
    - --root-ca-file=/etc/kubernetes/pki/ca.crt
    - --cluster-signing-key-file=/etc/kubernetes/pki/ca.key
    - --address=127.0.0.1
    - --leader-elect=true
    - --use-service-account-credentials=true
    image: k8s.gcr.io/kube-controller-manager-amd64:v1.10.1
    livenessProbe:
      failureThreshold: 8
      httpGet:
        host: 127.0.0.1
        path: /healthz
        port: 10252
        scheme: HTTP
      initialDelaySeconds: 15
      timeoutSeconds: 15
    name: kube-controller-manager
    resources:
      requests:
        cpu: 200m
    volumeMounts:
    - mountPath: /etc/kubernetes/pki
      name: k8s-certs
      readOnly: true
    - mountPath: /etc/ssl/certs
      name: ca-certs
      readOnly: true
    - mountPath: /etc/kubernetes/controller-manager.conf
      name: kubeconfig
      readOnly: true
    - mountPath: /usr/libexec/kubernetes/kubelet-plugins/volume/exec
      name: flexvolume-dir
  hostNetwork: true
  volumes:
  - hostPath:
      path: /etc/ssl/certs
      type: DirectoryOrCreate
    name: ca-certs
  - hostPath:
      path: /etc/kubernetes/controller-manager.conf
      type: FileOrCreate
    name: kubeconfig
  - hostPath:
      path: /usr/libexec/kubernetes/kubelet-plugins/volume/exec
      type: DirectoryOrCreate
    name: flexvolume-dir
  - hostPath:
      path: /etc/kubernetes/pki
      type: DirectoryOrCreate
    name: k8s-certs
status: {}

# cat kube-scheduler.yaml
apiVersion: v1
kind: Pod
metadata:
  annotations:
    scheduler.alpha.kubernetes.io/critical-pod: ""
  creationTimestamp: null
  labels:
    component: kube-scheduler
    tier: control-plane
  name: kube-scheduler
  namespace: kube-system
spec:
  containers:
  - command:
    - kube-scheduler
    - --address=127.0.0.1
    - --leader-elect=true
    - --kubeconfig=/etc/kubernetes/scheduler.conf
    image: k8s.gcr.io/kube-scheduler-amd64:v1.10.1
    livenessProbe:
      failureThreshold: 8
      httpGet:
        host: 127.0.0.1
        path: /healthz
        port: 10251
        scheme: HTTP
      initialDelaySeconds: 15
      timeoutSeconds: 15
    name: kube-scheduler
    resources:
      requests:
        cpu: 100m
    volumeMounts:
    - mountPath: /etc/kubernetes/scheduler.conf
      name: kubeconfig
      readOnly: true
  hostNetwork: true
  volumes:
  - hostPath:
      path: /etc/kubernetes/scheduler.conf
      type: FileOrCreate
    name: kubeconfig
status: {}

Prometheus Operator Logs:

$ kubectl logs -f prometheus-operator-74799957fd-4f2rm
ts=2018-04-27T10:17:28.360594955Z caller=operator.go:170 component=alertmanageroperator msg="connection established" cluster-version=v1.10.1
ts=2018-04-27T10:17:28.361390121Z caller=operator.go:269 component=prometheusoperator msg="connection established" cluster-version=v1.10.1
ts=2018-04-27T10:17:28.36618667Z caller=operator.go:184 component=alertmanageroperator msg="CRD API endpoints ready"
ts=2018-04-27T10:17:28.440964629Z caller=operator.go:283 component=prometheusoperator msg="CRD API endpoints ready"
ts=2018-04-27T10:17:28.448547688Z caller=operator.go:319 component=prometheusoperator msg="Prometheus added" key=default/prometheus
ts=2018-04-27T10:17:28.449569281Z caller=operator.go:339 component=prometheusoperator msg="Prometheus updated" key=default/prometheus
ts=2018-04-27T10:17:28.449503297Z caller=operator.go:684 component=prometheusoperator msg="sync prometheus" key=default/prometheus
ts=2018-04-27T10:17:28.457807736Z caller=operator.go:1024 component=prometheusoperator msg="updating config skipped, no configuration change"
ts=2018-04-27T10:17:28.588016535Z caller=operator.go:684 component=prometheusoperator msg="sync prometheus" key=default/prometheus
ts=2018-04-27T10:17:28.593928954Z caller=operator.go:1024 component=prometheusoperator msg="updating config skipped, no configuration change"
ts=2018-04-27T10:19:06.770025749Z caller=operator.go:684 component=prometheusoperator msg="sync prometheus" key=default/prometheus
ts=2018-04-27T10:19:06.776306715Z caller=operator.go:1024 component=prometheusoperator msg="updating config skipped, no configuration change"
ts=2018-04-27T10:19:21.802331777Z caller=operator.go:339 component=prometheusoperator msg="Prometheus updated" key=default/prometheus
ts=2018-04-27T10:19:21.802557867Z caller=operator.go:684 component=prometheusoperator msg="sync prometheus" key=default/prometheus
ts=2018-04-27T10:19:21.806284724Z caller=operator.go:1024 component=prometheusoperator msg="updating config skipped, no configuration change"
ts=2018-04-27T10:20:28.407405614Z caller=operator.go:684 component=prometheusoperator msg="sync prometheus" key=default/prometheus
ts=2018-04-27T10:20:28.439442559Z caller=operator.go:1024 component=prometheusoperator msg="updating config skipped, no configuration change"
ts=2018-04-27T10:20:34.930775038Z caller=operator.go:339 component=prometheusoperator msg="Prometheus updated" key=default/prometheus
ts=2018-04-27T10:20:34.93085489Z caller=operator.go:684 component=prometheusoperator msg="sync prometheus" key=default/prometheus
ts=2018-04-27T10:20:34.93633399Z caller=operator.go:1024 component=prometheusoperator msg="updating config skipped, no configuration change"

The blog post is outdated, sorry about that, it happens easily to blog posts to go stale. Please try the getting started guide and see if you still run into problems.

just this problem:
level=error ts=2018-04-28T02:43:34.390567729Z caller=main.go:216 component=k8s_client_runtime err="github.com/prometheus/prometheus/discovery/kubernetes/kubernetes.go:270: Failed to list *v1.Pod: pods is forbidden: User \"system:serviceaccount:default:default\" cannot list pods in the namespace \"default\""
level=error ts=2018-04-28T02:43:34.390781165Z caller=main.go:216 component=k8s_client_runtime err="github.com/prometheus/prometheus/discovery/kubernetes/kubernetes.go:269: Failed to list *v1.Service: services is forbidden: User \"system:serviceaccount:default:default\" cannot list services in the namespace \"default\""
level=error ts=2018-04-28T02:43:34.394814697Z caller=main.go:216 component=k8s_client_runtime err="github.com/prometheus/prometheus/discovery/kubernetes/kubernetes.go:268: Failed to list *v1.Endpoints: endpoints is forbidden: User \"system:serviceaccount:default:default\" cannot list endpoints in the namespace \"default\""

and can be solve by：
kubectl apply -f default-privilege-add.yaml

default-privilege-add.yaml look like:
---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRole
metadata:
  name: default-privilege-add
rules:
- apiGroups: [""]
  resources:
  - endpoints
  - services
  - pods
  verbs: ["get", "list", "watch"]

---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRoleBinding
metadata:
  name: default-privilege-add
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: default-privilege-add
subjects:
- kind: ServiceAccount
  name: default
  namespace: default

Actually looking at the getting started once more, we just forgot or seem to have removed the “serviceAccountName: prometheus” as the cluster role and binding you are describing are basically what is described in the “Enable RBAC rules for Prometheus pods” section.

authors: brancz gogeof

repo: coreos/prometheus-operator


text:
Add README for kube-prometheus helm chart

Would love to have a README with a couple examples of how to get the kube-prometheus helm chart running successfully.
Something similar to: https://github.com/coreos/prometheus-operator/blob/master/helm/prometheus/README.md

@ryanwalls I had the same issue on the first time I deployed kube-prometheus. I'm pretty sure this is related to https://github.com/coreos/prometheus-operator/issues/443#issuecomment-311046540.
Could you try to reinstall prometheus with the right serviceMonitorSelector?
helm install --name prometheus --set serviceMonitorsSelector.app=prometheus prometheus

@gianrubio Which issue are you referring to?
Also, I'm using the kube-prometheus chart, so I'm not explicitly installing the prometheus chart.

Does anyone managed to install kube-prometheus chart? I alway have an error of: Error: apiVersion "monitoring.coreos.com/v1" in kube-prometheus/charts/exporter-kubernetes/templates/servicemonitor.yaml is not available

@burdiyan it's your first time running the charts? If the answer is not, you probably have some garbage from previous version.
I would recommend you to:

Purge the charts running: ``` helm delete --purge chart-name````
Remove all the crd or thirdypartyresource.

kubectl delete crd (or thirdypartyresource) prometheuses.monitoring.coreos.com
kubectl delete crd (or thirdypartyresource) servicemonitors.monitoring.coreos.com
kubectl delete crd (or thirdypartyresource) alertmanagers.monitoring.coreos.com

Reinstall the chart

let me know if this fix you setup.

@gianrubio That was my first attempt to install the chart in a brand new GKE cluster.

Do you have prometheus-operator installed? Try to install it first and after that install kube-prometheus.
Also please post the output of
kubectl get pods,jobs -n monitoring

@gianrubio Yeah, that was the error, and I just figured out that you have to install the operator first. Worth mentioning on the README of kube-prometheus chart I believe.
Thanks a lot, anyway!

Does someone want to add a troubleshooting section or something to the helm readme? Maybe we can add some examples as well, as suggested in the beginning of the thread.

I can do it after all the rework on helm, btw I mapped this dependency on my todo list

@burdiyan you seem to have experienced the same problem i did: are you using quay.io/coreos/prometheus-operator:v0.11.3 on k8s 1.6.x ?
if that's the case, then this PR should solve it: https://github.com/coreos/prometheus-operator/pull/829

@gianrubio how does it work that one's supposed to install the operathor first to then install kube-prometheus? I though [this chart dependency[(https://github.com/coreos/prometheus-operator/blob/master/helm/kube-prometheus/requirements.yaml#L7-L10) would take care of that

@odino I guess master branch is not yet published to the CoreOS chart repository, and in previous versions this requirement was not there yet.

gotcha!

This should now be fixed, we are now automatically uploading new versions as they are bumped and merged.

@brancz Thanks for getting the latest versions synced up! Can this issue remain open until the original concern is addressed of adding information to the readme on how to actually use the charts? I'm installing via the scripts right now and would prefer to move to the chart but not really sure how to do it.

Thanks for your response. I’m fine with re-opening for that purpose.

@jordanjennings There is an official helm chart that can be deployed all in one go now. It may still require some documentation to be complete, but I'm happy to address your concerns there if you are prepared to move to that version

Since we don't support the helm chart in this repo anymore, closing this issue. Feel free to open a new one if you think it's not valid, thanks!

authors: brancz burdiyan gianrubio jordanjennings lilic mbenabda odino ryanwalls vsliouniaev


text:
add additionalAlertManagerConfigs to helm chart

This should help Helm users take advantage of the flexibility of the additionalAlertManagerConfigs field added to PrometheusSpec.
Fixes #1456

anyone have an idea about the failing check? it appears to be an issue with the CI pipeline unless i'm misunderstanding the error messages

The chart version needs to be bumped, please refer to how to contribute. Thanks! :slightly_smiling_face:

lgtm on green

thanks @alice-sawatzky

authors: alice-sawatzky brancz gianrubio


text:
build: Add configure flags for controlling tpm logging

It is enabled by default to follow the secure-by-default principle.
CI platforms are unlikely to have the headers installed, so we enable
TPM conditionally.
Fixes #1815.

What about Documentation/devel/release.md, should it use --enable-tpm=auto? I guess not, to be sure TPM is enabled in the releases.
Does it have run-time dependencies?

What about Documentation/devel/release.md, should it use --enable-tpm=auto? I guess not, to be sure TPM is enabled in the releases.

Right. For now we just continue if we fail to log to tpm, so it still should work for users without TPM.

Does it have run-time dependencies?

I guess that there is some daemon which handles writing stuff into TPM. See https://github.com/coreos/rkt/blob/master/pkg/tpm/tpm.go#L25

I don't know if we should merge this now because of https://github.com/coreos/rkt/issues/1816#issuecomment-172875302

Should rkt version say whether it was build with tpm? (question related to #1998)

Moving milestone for now, until we know the outcome of https://github.com/coreos/go-tspi/issues/3

I don't care about this getting into 1.0 so I've bumped the milestone. I do, however, want a fix for #1816 to happen.

Sorry, I was a little hasty and misunderstood. I think we can land this without being dependent on coreos/go-tspi#3 (rather, we could have #1816 in place). Moving back to 1.0..

Updated. The unanswered question for now is whether rkt binary in new releases should depend on trousers.

This needs to be updated following the merge of this commit: https://github.com/coreos/rkt/commit/5e8ac50448d06b8fed7f172771c2e3899e548957

Updated. The unanswered question for now is whether rkt binary in new releases should depend on trousers.

I think we should build without for now for the release on GitHub. But make it very clear how to enable it, and do so in the CoreOS build.

[ ] use --enable-tpm=no in the release guidelines

Bah, didn't notice the checkbox about TPM in rkt version.

LGTM and Semaphore is green.

Updated with printing the features. The features also also printed in configure instead of "TPM enabled" now.

LGTM.
For some reason, the green Semaphore logo has not been updated on this PR but Semaphore has completed with success: https://semaphoreci.com/coreos/rkt/branches/pull-request-1996/builds/8

authors: alban blixtra iaguis jonboulle krnowak

repo: coreos/rkt


text:
use go 1.6 and regex updates for 'go version'

The current 'go version' in fedora rawhide is '1.6rc1'. This version string
doesn't get correctly parsed by the configure script and it terminates
saying, "configure: error: *** go is too old (go version go1.6rc1 linux/amd64".
This commit allows all golang versions to be correctly detected.
Signed-off-by: Lokesh Mandvekar lsm5@fedoraproject.org
Not certain off-hand if rkt is Go 1.6 ready but PTAL :)

It's ok to accept Go 1.6 but it should not break Go 1.4 and Go 1.5 :)

@lsm5 Thanks for the testing on Fedora rawhide and the patch. This break the build on current go version. I updated your patch in: https://github.com/coreos/rkt/pull/2057

@alban strange, it did work for me on rhel with go 1.4.2, but whatevs :) ..glad the issue's gotten noticed, thanks!


text:
Error 403 when saving settings at /wp-admin/index.php?page=aioseo-setup-wizard#/category

path:
example.com/wp-admin/index.php?page=aioseo-setup-wizard#/category
Clicking save button causes endless animation of button without any further visual results or changes.
Log file of modsecurity reports error 403
Log file of accesslog reports error 403
---0axHjVCS---A--

[17/May/2021:23:48:52 +0200] 162128813271.917277 yyy.yyy.yyy.yyy 57906 xxx.xxx.xxx.xxx 80

---0axHjVCS---B--

POST /wp-json/aioseo/v1/wizard HTTP/1.1

Accept-Encoding: gzip, deflate

Cookie: _fbp=fb.1.1598866358706.1826547220; _ga=GA1.2.771664089.1598866361; ajs_anonymous_id=%22101e7a5c-754e-4d63-b61a-6428795a136f%22; _hjid=ef1192b3-fbb7-43f5-a616-be9a9596bbce; ajs_user_id=%22ps.-server.example.com%22; mp_c8aed77ebc880f4222724bc14a0d8a0d_mixpanel=%7Bmixerstinct_id%22%3A%20%22ps.example.com%22%2C%22%24device_id%22%3A%20%22178be0130ab701-07999816b59176-3b7f0650-1e6d71-178be0130acc07%22%2C%22mp_lib%22%3A%20%22Segment%3A%20web%22%2C%22%24initial_referrer%22%3A%20%22http%3A%2F%2Fps.example.com%2Fadmin383sagpej%2Findex.php%3Fcontroller%3DAdminLogin%26token%3D01bdc31380f2a324e1e264a6f96e0a0a%22%2C%22%24initial_referring_domain%22%3A%20%22ps.example.com%22%2C%22%24user_id%22%3A%20%22ps.example.com%22%2C%22mp_name_tag%22%3A%20%22ps.example.com%22%2C%22language%22%3A%20%22pl%22%2C%22version_ps%22%3A%20%221.7.7.3%22%2C%22version_module%22%3A%20%221.3.3%22%2C%22module%22%3A%20%22ps_metrics%22%2C%22id%22%3A%20%22ps.example.com%22%2C%22%24first_name%22%3A%20%22http%3A%2F%2Fps.example.com%2F%22%2C%22%24name%22%3A%20%22http%3A%2F%2Fps.example.com%2F%22%7D; __gads=ID=71d0a2c6958f4bd3-2206138a1ebb007b:T=1618482997:RT=1618482997:S=ALNI_MbK6goyCUI9Bso4GoeyiXaUMboN2w; wordpress_test_cookie=WP+Cookie+check; wordpress_logged_in_72a0324d9c077ad9cef625af54565376=test%7C1621460657%7CtyexE0B7mf5fOnWAB6SJCfDrg5aphEQ2KnLdCSpFL6G%7C7d909892951568e131dcaa2c3d304712688e8233ae1e0943d87ec4851faf012a; wp-settings-time-1=1621287870; wp-settings-1=libraryContent%3Dbrowse

Referer: http://example.com/wp-admin/index.php?page=aioseo-setup-wizard

Origin: http://example.com

Accept: */*

User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 Safari/537.36

Content-Type: application/json

X-WP-Nonce: cc9587282c

Accept-Language: pl-PL,pl;q=0.9,en-US;q=0.8,en;q=0.7

Content-Length: 1326

Connection: keep-alive

Host: example.com

---0axHjVCS---D--

---0axHjVCS---E--

\x0d\x0a<title>403 Forbidden</title>\x0d\x0a\x0d\x0a
403 Forbidden
\x0d\x0a
nginx\x0d\x0a\x0d\x0a\x0d\x0a\x0d\x0a\x0d\x0a\x0d\x0a\x0d\x0a\x0d\x0a\x0d\x0a

---0axHjVCS---F--

HTTP/1.1 403

Server: nginx

Date: Mon, 17 May 2021 21:48:52 GMT

Content-Length: 548

Content-Type: text/html

Connection: keep-alive

---0axHjVCS---H--

ModSecurity: Warning. Matched "Operator `PmFromFile' with parameter `lfi-os-files.data' against variable `ARGS_NAMES:json.wizard.additionalInformation.social.profiles.sameUsername.included.array_2' (Value: `json.wizard.additionalInformation.social.profiles.sameUsername.included.array_2' ) [file "/usr/local/etc/nginx/modsecurity/coreruleset/rules/REQUEST-930-APPLICATION-ATTACK-LFI.conf"] [line "78"] [id "930120"] [rev ""] [msg "OS File Access Attempt"] [data "Matched Data: .profile found within ARGS_NAMES:json.wizard.additionalInformation.social.profiles.sameUsername.included.array_2: json.wizard.additionalinformation.social.profiles.sameusername.included. (7 characters omitted)"] [severity "2"] [ver "OWASP_CRS/3.3.0"] [maturity "0"] [accuracy "0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-lfi"] [tag "paranoia-level/1"] [tag "OWASP_CRS"] [tag "capec/1000/255/153/126"] [tag "PCI/6.5.4"] [hostname "xxx.xxx.xxx.xxx"] [uri "/wp-json/aioseo/v1/wizard"] [unique_id "162128813271.917277"] [ref "o40,8v0,64t:utf8toUnicode,t:urlDecodeUni,t:normalizePathWin,t:lowercaseo40,8v0,67t:utf8toUnicode,t:urlDecodeUni,t:normalizePathWin,t:lowercaseo40,8v0,68t:utf8toUnicode,t:urlDecodeUni,t:normalizePathWi (1220 characters omitted)"]

ModSecurity: Access denied with code 403 (phase 2). Matched "Operator `Ge' with parameter `50' against variable `TX:ANOMALY_SCORE' (Value: `100' ) [file "/usr/local/etc/nginx/modsecurity/coreruleset/rules/REQUEST-949-BLOCKING-EVALUATION.conf"] [line "80"] [id "949110"] [rev ""] [msg "Inbound Anomaly Score Exceeded (Total Score: 100)"] [data ""] [severity "2"] [ver "OWASP_CRS/3.3.0"] [maturity "0"] [accuracy "0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-generic"] [hostname "xxx.xxx.xxx.xxx] [uri "/wp-json/aioseo/v1/wizard"] [unique_id "162128813271.917277"] [ref ""]

---0axHjVCS---I--

---0axHjVCS---J--

---0axHjVCS---Z--

Environment
CRS version (e.g., v3.2.0): 3.30

Paranoia level setting: 1
ModSecurity version (e.g., 2.9.3):  3
Web Server and version (e.g., apache 2.4.41):  nginx  1.18.0
Operating System and version:  FreeBSD 12.2-RELEASE  amd64

Thank you for reporting @issuesreporting.
I confirm your finding:
curl localhost -d "json.wizard.additionalInformation.social.profiles.sameUsername.included.array_2=foo"

This call triggers rule 930120: OS File Access Attempt.

Thank you for confirmation. Is there any sort of additional information I can support you with that may be helpful?

Yes, your audit log reports an anomaly score of 100 in rule 949110, yet the log only brings a single alert on 930120 that in a normal installation accounts for an anomaly score of 5. Did you remove rule alerts that account for remaining anomaly score of 95?

additionally backend log of httpd reports following
2021/05/21 14:28:29 [error] 46007#101979: *36192868 [client yyy.yyy.yyy.yyy] ModSecurity: Access denied with code 403 (phase 2). Matched "Operator `Ge' with parameter `50' against variable `TX:ANOMALY_SCORE' (Value: `100' ) [file "/usr/local/etc/nginx/modsecurity/coreruleset/rules/REQUEST-949-BLOCKING-EVALUATION.conf"] [line "80"] [id "949110"] [rev ""] [msg "Inbound Anomaly Score Exceeded (Total Score: 100)"] [data ""] [severity "2"] [ver "OWASP_CRS/3.3.0"] [maturity "0"] [accuracy "0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-generic"] [hostname "xxx.xxx.xxx.xxx"] [uri "/wp-json/aioseo/v1/wizard"] [unique_id "162160010976.027469"] [ref ""], client: yyy.yyy.yyy.yyy, server: _, request: "POST /wp-json/aioseo/v1/wizard HTTP/1.1", host: "example.com", referrer: "http://example.com/wp-admin/index.php?page=aioseo-setup-wizard"

Thank you. But this is the expected repetition of the rule alert 949110 above. It does not say how you end up with a score of 100.
Would you mind grepping for 162160010976.027469 in the backend log? That should return every rule alert triggered by this request.

I would like to make a correction, I see that I wrote about backend, but in reality it was frontend log file. The line presented in previous post.
As for other information - only that from modsecurity log is present. No more files of any sort, unless I'm missing something out.
Exactly
---mmeSv661---A--
[21/May/2021:14:28:29 +0200] 162160010976.027469 yyy.yyy.yyy.yyy 45530 xxx.xxx.xxx.xxx 80
---mmeSv661---B--
POST /wp-json/aioseo/v1/wizard HTTP/1.1
Accept-Encoding: gzip, deflate
Cookie: _fbp=fb.1.1598866358706.1826547220; _ga=GA1.2.771664089.1598866361; ajs_anonymous_id=%22101e7a5c-754e-4d63-b61a-6428795a136f%22; _hjid=ef1192b3-fbb7-43f5-a616-be9a9596bbce; ajs_user_id=%22ps.example.com%22; mp_c8aed77ebc880f4222724bc14a0d8a0d_mixpanel=%7B%22distinct_id%22%3A%20%22ps.example.com%22%2C%22%24device_id%22%3A%20%22178be0130ab701-07999816b59176-3b7f0650-1e6d71-178be0130acc07%22%2C%22mp_lib%22%3A%20%22Segment%3A%20web%22%2C%22%24initial_referrer%22%3A%20%22http%3A%2F%2Fps.example.com%2Fadmin383sagpej%2Findex.php%3Fcontroller%3DAdminLogin%26token%3D01bdc31380f2a324e1e264a6f96e0a0a%22%2C%22%24initial_referring_domain%22%3A%20%22ps.example.com%22%2C%22%24user_id%22%3A%20%22ps.example.com%22%2C%22mp_name_tag%22%3A%20%22ps.example.com%22%2C%22language%22%3A%20%22pl%22%2C%22version_ps%22%3A%20%221.7.7.3%22%2C%22version_module%22%3A%20%221.3.3%22%2C%22module%22%3A%20%22ps_metrics%22%2C%22id%22%3A%20%22ps.example.com%22%2C%22%24first_name%22%3A%20%22http%3A%2F%2Fps.example.com%2F%22%2C%22%24name%22%3A%20%22http%3A%2F%2Fps.example.com%2F%22%7D; __gads=ID=71d0a2c6958f4bd3-2206138a1ebb007b:T=1618482997:RT=1618482997:S=ALNI_MbK6goyCUI9Bso4GoeyiXaUMboN2w; wordpress_test_cookie=WP+Cookie+check; wp-settings-time-1=1621287870; wp-settings-1=libraryContent%3Dbrowse; wordpress_logged_in_72a0324d9c077ad9cef625af54565376=test%7C1621772877%7CD5XTBc13FUjAizshH29AUNrp0oK53O23X7n22usNFIE%7C25c406d3568e0decfba0cb7eeb5635585b17a5f4646ca476a131726524d07a68
Referer: http://login-server2.example.com/wp-admin/index.php?page=aioseo-setup-wizard
Origin: http://login-server2.example.com
Accept: */*
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 Safari/537.36
Content-Type: application/json
X-WP-Nonce: f4606f595e
Accept-Language: pl-PL,pl;q=0.9,en-US;q=0.8,en;q=0.7
Content-Length: 1334
Connection: keep-alive
Host: login-server2.example.com---mmeSv661---D-----mmeSv661---E--
\x0d\x0a<title>403 Forbidden</title>\x0d\x0a\x0d\x0a
403 Forbidden
\x0d\x0a
nginx\x0d\x0a\x0d\x0a\x0d\x0a\x0d\x0a\x0d\x0a\x0d\x0a\x0d\x0a\x0d\x0a\x0d\x0a---mmeSv661---F--
HTTP/1.1 403
Server: nginx
Date: Fri, 21 May 2021 12:28:29 GMT
Content-Length: 548
Content-Type: text/html
Connection: keep-alive---mmeSv661---H--
ModSecurity: Warning. Matched "Operator `PmFromFile' with parameter `lfi-os-files.data' against variable `ARGS_NAMES:json.wizard.additionalInformation.social.profiles.sameUsername.included.array_2' (Value: `json.wizard.additionalInformation.social.profiles.sameUsername.included.array_2' ) [file "/usr/local/etc/nginx/modsecurity/coreruleset/rules/REQUEST-930-APPLICATION-ATTACK-LFI.conf"] [line "78"] [id "930120"] [rev ""] [msg "OS File Access Attempt"] [data "Matched Data: .profile found within ARGS_NAMES:json.wizard.additionalInformation.social.profiles.sameUsername.included.array_2: json.wizard.additionalinformation.social.profiles.sameusername.included. (7 characters omitted)"] [severity "2"] [ver "OWASP_CRS/3.3.0"] [maturity "0"] [accuracy "0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-lfi"] [tag "paranoia-level/1"] [tag "OWASP_CRS"] [tag "capec/1000/255/153/126"] [tag "PCI/6.5.4"] [hostname "xxx.xxx.xxx.xxx"] [uri "/wp-json/aioseo/v1/wizard"] [unique_id "162160010976.027469"] [ref "o40,8v0,64t:utf8toUnicode,t:urlDecodeUni,t:normalizePathWin,t:lowercaseo40,8v0,67t:utf8toUnicode,t:urlDecodeUni,t:normalizePathWin,t:lowercaseo40,8v0,68t:utf8toUnicode,t:urlDecodeUni,t:normalizePathWi (1220 characters omitted)"]
ModSecurity: Access denied with code 403 (phase 2). Matched "Operator `Ge' with parameter `50' against variable `TX:ANOMALY_SCORE' (Value: `100' ) [file "/usr/local/etc/nginx/modsecurity/coreruleset/rules/REQUEST-949-BLOCKING-EVALUATION.conf"] [line "80"] [id "949110"] [rev ""] [msg "Inbound Anomaly Score Exceeded (Total Score: 100)"] [data ""] [severity "2"] [ver "OWASP_CRS/3.3.0"] [maturity "0"] [accuracy "0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-generic"] [hostname "xxx.xxx.xxx.xxx"] [uri "/wp-json/aioseo/v1/wizard"] [unique_id "162160010976.027469"] [ref ""]---mmeSv661---I-----mmeSv661---J-----mmeSv661---Z--

I will add this to the WordPress exclusions package.

We talked about this issue at our recent project meeting.
Decision: @lifeforms will take this on and do the fix. As an addendum, we are OK with covering WP plugins in Rule Exclusion packages.

Ping @lifeforms ...

@lifeforms, would you like to schedule this for the chat tonight and we reassign it to somebody else?

Sorry for the late comment, I created a PR in #2311.

authors: dune73 issuesreporting lifeforms

repo: coreruleset/coreruleset

license_source: bigquery


text:
chore: create changelog PRs weekly, based on main

The idea to base changelog PRs off each other didn't work out. Merging a newer changelog PR before its older predecessor led to a ton of conflicts. This PR reverts to the previous behavior of basing all changelog PRs on the main branch.
In order to reduce the workload, changelog PRs are now created weekly on Sunday.
In order to improve handling and debugging, PRs are checked against previously merged changelog PRs and excluded if found.
The workflow can now be manually triggered from the GitHub UI. This operation is safe because the PRs are checked agains previous changelog PRs.

@dune73 @fzipi, the schedule for creating changelog PRs is now once per week, Sunday night. I chose that in order to get everyone to update the changelog before the CRS chats. I'm aware that this might conflict with the release schedule. On the other hand, the workflow can now be triggered manually, so we could do that as part of the release process.
Thoughts?

Let's give this a shot.


text:
[v3-pro] c-show and c-active not set for extended path

c-show and c-active are not automatically set if the path does not match 100%
c-show and c-active are added: /account/
c-show and c-active are not added: /account/password/

        Account

                Profile

Operating system and version: macOS 10.15.6
Browser and version: Firefox 79.0 (64-Bit)

Fixed in v3.3.0

Nothing changed in https://www.npmjs.com/package/@coreui/coreui-pro v3.3.0.
Problem is still there.

@mrholek Still not working! Where can I find the change?

v3.4.0: Still not working!

@mrholek Please reopen the issue!

I changed:

Default$b.activeLinksExact to false (line 9528, coreui.bundle.js)
element.href.startsWith(currentUrl) to currentUrl.startsWith(element.href) (line 9956, coreui.bundle.js)

Same for v4.1-pro

authors: mrholek wittfabian

repo: coreui/coreui

license: MIT


text:
sidebar link doesn't activate when url has  a hash.

I think there is a mistake in the regular expression listed in the _setActiveLink function in file sidebar.js.
-        var urlHasParams = /\\?.*=/;
-        var urlHasQueryString = /\\?./;
+       var urlHasParams = /\?.*=/;
+       var urlHasQueryString = /\?./;

@0xcdcdcdcd can you paste me an example url?

"dashboard" menu doesn't activate.
sample.zip

If you want to use CoreUI with Vue.js you should try the dedicated version https://github.com/coreui/coreui-vue

I attached a simple hash sample.
sample2.zip


text:
Switch from ApprovalTests to VerifyTests for golden master testing

This replaces, ApprovalTests, the library that's being used for golden master testing with VerifyTests.
This switch is primarily motivated by challenges that have popped up because of how the ApprovalTests library formats the .received.txt that it generates. When the file that's generated by ApprovalTests contains multiple lines, for example when the contents of an array are being verified, then ApprovalTests uses the newline character \n to separate those lines, even when the test is running on a Windows OS while the typical line separator is \r\n.
A secondary benefit is that the output format used by VerifyTests is "based on" JSON. Which makes the files much easier to read the very large amount of data that is being verified by these tests. Hopefully, this will provide benefits when tracking down bugs that might result in a single value in the file being incorrect.

This might help address the current failure in PR #405 when the tests are being run on Windows.

repo: corgibytes/freshli-lib


text:
[Bug] @cornerstonejs/tools/dist/types/utilities/getViewportForAnnotation.d.ts:2:141 - error TS2307: Cannot find module 'packages/core/dist/types/types' or its corresponding type declarations.

Describe the Bug
File getViewportsForAnnotation.d:
import type { Annotation } from '../types';
export default function getViewportsForAnnotation(annotation: Annotation): (import("packages/core/dist/types/types").IVolumeViewport | import("packages/core/dist/types/types").IStackViewport)[];
Has "packages/core/dist/types/types".
File getViewportForAnnotation.d.ts :
import type { Annotation } from '../types';
export default function getViewportForAnnotation(annotation: Annotation): import("packages/core/dist/types/types").IVolumeViewport | import("packages/core/dist/types/types").IStackViewport;
The directory "packages" does not exist.
Steps to Reproduce
install @cornerstonejs/tools^1.70.5
The current behavior
@cornerstonejs/tools/dist/types/utilities/getViewportForAnnotation.d.ts:2:141 - error TS2307: Cannot find module 'packages/core/dist/types/types' or its corresponding type declarations.
The expected behavior
No build error
OS
Windows 11
Node version
v18.19.0
Browser
N/A

I cannot reproduce the error. Try looking if you've already done it https://www.cornerstonejs.org/docs/getting-started/installation.

Not sure what to add. I went in directly and changed "packages/core/dist/types/types" to "core/dist/types/types" and it worked fine. I did follow the installation directions as suggested.
This works for me now, so I'll just push forward until I hit this issue again.

Hey all - also getting the same error when updating to the latest tools version
Here is a StackBlitz creating the error
https://stackblitz.com/edit/c3d-tools-type-error?file=index.ts
The issue is in this file
'/@cornerstonejs/tools/dist/types/utilities/getViewportForAnnotation.d.ts'
Its referring to an internal package (packages/core/dist/types/types) rather than the cornerstonejs package
The fix is to change the import(s) from  packages/core/dist/types/types  to @cornerstonejs/core/dist/types/types

I get the same error.
As a temporary fix, I modified the tsconfig.json:
I added this line:
"packages/core/dist/types/types": ["node_modules/@cornerstonejs/core/dist/types/types"] in "compilerOptions" / "paths"


text:
Current state of community-developed alternatives

This issue aims to supersede #75 as discussed in https://github.com/corona-warn-app/cwa-website/pull/1070#discussion_r613822148 by providing clear and concise up-to-date information regarding alternative CWA-compatible clients developed by the community. I opened this issue in the Android repository because it discusses solutions specifically for the Android platform.
End-user applications
This list displays installable Android client software.

Name
Repository
Website
License
Status
Additional information
Maintainers

Corona Contact Tracing Germany
https://codeberg.org/corona-contact-tracing-germany/cwa-android/

Apache 2.0
Active
Depends on microG EN libraries
@Bubu, @fynngodau

CoraLibre
https://github.com/CoraLibre/CoraLibre-android
https://coralibre.de
Apache 2.0
Not production-ready, discontinued
Depends on CoraLibre-android-sdk, discussed in #75
cosee GmbH

Libraries
Here you can find all libraries that are aiming to provide a replacement to the proprietary Google EN library.

Name
Repository
Website
License
Status
Additional information
Maintainers

microG
https://github.com/microg/GmsCore/
https://microg.org
Apache 2.0
Active
Modules play-services-nearby-core and play-services-nearby-core-ui contain the relevant code
@mar-v-in

CoraLibre-android-sdk
https://github.com/CoraLibre/CoraLibre-android-sdk

MPL 2.0
Discontinued

cosee GmbH

Please contact me (through this issue or otherwise) if any implementation that I am not aware of is missing here or if anything else is incorrect.

Internal Tracking ID: EXPOSUREAPP-6497

@fynngodau
Thank you. This is now tracked as EXPOSUREAPP-6497

Corona-Warn-App Open Source Team

authors: fynngodau heinezen

repo: corona-warn-app/cwa-app-android


text:
After factory reset / backup: infinite loop with the on boarding screens

Avoid duplicates

[x] Bug is not mentioned in the FAQ
[x] Bug is not already reported in another issue

Describe the bug
After a change to a new iPhone and automated re-installation from the backup, I'm stuck in an infinite loop with the welcome / on boarding screens.
I can click through the 5 screens but than I'm back on the first screen again.
Expected behaviour
After clicking through the five screens, I should jump to the home screen of CWA.
Steps to reproduce the issue

Use a new iPhone (factory reset should also work)
Login with your Apple ID
Select use backup to configure iPhone
Wait till CWA is installed and settings are restored from the backup
Open CWA
And you are in an infinite loop with the on boarding screens.

Technical details

iOS Version: 13.7
Device: iPhone SE 2020

Possible Fix
Additional context
Uninstalling the app and re-installation via App Store helped to solve the issue, but my data is lost.
On the old device (iPhone 7, iOS 13.7) there was:

Risk Assessment active
Warnings / Notifications allowed

Duplicate of: https://github.com/corona-warn-app/cwa-app-ios/issues/754

Please also see the related FAQ entry:
https://www.coronawarn.app/en/faq/?search=Backup#migration_Apple

Duplicate of #754

authors: Ein-Tim heinezen rainervonuns

repo: corona-warn-app/cwa-app-ios


text:
Translation Delivery

Translation Delivery

This pull request is for translation delivery. Please review and approve them.


text:
Update appToWebLinks.json for 2.28 release

This PR carries out housekeeping for the appToWebLinks.json data source for the Cypress test cypress/integration/app_to_web.js.

The comment field appVersionLast is updated to 2.28 to show that the file has been prepared for the upcoming release
The #mask_rules entry, which was added for the 2.27 release, is moved into alphabetical order for better readability and maintenance

Note that although the use of the FAQ anchor #quarantine_measures is planned to be removed in the CWA 2.28 release, it stays in the appToWebLinks.json file because the Cypress test ensures that all anchors used by previous app versions from "appVersionFirst": "2.23" onwards continue to be available. This could only change if there were to be a decision to stop supporting earlier app versions.

@MikeMcC399 Thanks for taking care of this!

repo: corona-warn-app/cwa-website


text:
Legal Notice not Translated German

Avoid duplicates

[x] This issue has not already been raised before

Current Implementation

The entire app is in German, but the legal notes are displayed in English.
Suggested Enhancement

For a better understanding, these should also be displayed in German.

Internal Tracking Id: EXPOSUREAPP-2075

Is there any update available on this? Has this request been declined or just not looked at yet?
In version 2.5.1 under iOS the "Rechtliche Hinweise" section is still displayed only in English.

authors: Ein-Tim ElOxo

repo: corona-warn-app/cwa-wishlist


text:
Windows frame timer fix

This is a fix for the issue brought up here. Basically, the simulator will occasionally crash when you relaunch or close.
There's a possibility it's related to this, but that will need some follow-up to confirm. I was testing using a project that did have audio, although I thought it had occurred in quiet ones too. In any case, it wouldn't be unreasonable that audio updates might exacerbate timer issues.

Details:
Basically, it seems KillTimer does not actually evict relevant WM_TIMER messages from the queue, in which case they will still fire. There are vague hints of this in some online forum questions, but it's never spelled out. The problem in our case is that this might be after WinTimer's destructor has gone off, so everything in our timer callback is garbage.
As mentioned in #402, it looks like the network library basically reused the Rtt_WinTimer code, apart from not assigning the timer to a window. Furthermore, it uses an ID → timer map, using this in the callback to check if the timer still exists. I assume the same issue was being addressed.
I also mentioned in #402 that the wrong value was being passed to KillTimer(). This is per the SetTimer docs: "If the function succeeds and the hWnd parameter is not NULL, then the return value is a nonzero integer. An application can pass the value of the nIDEvent parameter to the KillTimer function to destroy the timer." and also those for KillTimer: "The timer to be destroyed. If the window handle passed to SetTimer is valid, this parameter must be the same as the nIDEvent
value passed to SetTimer."
I don't know what happens if this is wrong, but I figure it didn't amount to much because the timer was basically used for the entire run of a Solar program and went away when the window did, on close / relaunch. But in theory WinTimer is now more robust for wider use, with the revisions in this PR.
The changes are a lot like what network does. A map from ID → timer makes sure spurious callbacks do nothing. I used an incrementing ID (starting from 1) rather than what SetTimer returns ("If the function succeeds and the hWnd parameter is not NULL, then the return value is a nonzero integer."), since I'm not sure if that's recycled; for the same reason I didn't use a std::set, for the rare-but-possible case that another timer were reallocated into that same memory. These concerns are a bit academic with the timer being a singleton used from launch to close / relaunch, but it's not at all impossible that timers could be put to wider use. 😄

Moved to unordered_map just to prevent all the warnings.

authors: Shchvova ggcrunchy

repo: coronalabs/corona


text:
feature: createSpan should use event time instead of processing time

https://github.com/coroot/coroot-node-agent/blob/a90fb2df6441b31b0640c63ed60f6a6ab0860bb7/tracing/tracing.go#L90
There may be micro difference betweentime.Now() and the time when connection closed, the former is the processing time, and the latter is the event time. The duration between these two timestamps is used for agent handling.

Here is my idea.
eBPF program can get the time since boot, by calling bpf_ktime_get_boot_ns. We can record it as event_ktime.
GoLang program can also get the time since boot, by wrapping  the clock_gettime syscall. We can record it as process_ktime. Here is a GoLang demo:
func getMonotonicTime() {
	const CLOCK_MONOTONIC = 1 // CLOCK_MONOTONIC is the identifier for the monotonic clock in Linux.
	var ts syscall.Timespec
	_, _, errCode := syscall.Syscall(syscall.SYS_CLOCK_GETTIME, CLOCK_MONOTONIC, uintptr(unsafe.Pointer(&ts)), 0)
	if errCode != 0 {
		fmt.Printf("Failed to call SYS_CLOCK_GETTIME.\n")
		return
	}

	fmt.Printf("Monotonic time since boot is: %d seconds, %d nanoseconds.\n", ts.Sec, ts.Nsec)

	duration, err := time.ParseDuration(fmt.Sprintf("%ds%dns", ts.Sec, ts.Nsec))
	if err != nil {
		return
	}
	fmt.Printf("That's about %d minutes\n", int(duration.Minutes()))
}

Obviously GoLang program can get the well clock time through the now() function. We can record it as process_time.
So the accurate well clock time when l7_event emitted from the tracepiont event_time = process_time - process_ktime + event_ktime.

repo: coroot/coroot-node-agent


text:
support cmake LIBRARY_OUTPUT_PATH and EXECUTABLE_OUTPUT_PATH for rust cdylib

I found that when set rust to cdylib, the .dll can not generated at the same dir of LIBRARY_OUTPUT_PATH set by cmake.

Could you please give more details on what you have tried, and how it worked out (or rather didn't)?

cpp_rust.zip
consider this demo, the rust lib format is "cdylib", set camke binary output dir is /bin, by EXECUTABLE_OUTPUT_PATH and LIBRARY_OUTPUT_PATH set to /bin, but only cpp executable binary in /bin, the librust.dylib/rust.dll not output in bin

.

To me this looks like a duplicate of #65.

authors: eric5f3759df jschwe ratijas

repo: corrosion-rs/corrosion


text:
Calendar date picker not shown as a whole if you resize your tab or use the screen as split screen

Description of the bug
When you use your screen as a split screen and you want to have two browsers open on the half of the page, the calendar date picker is cutted out and not shown as a whole.
Reproduction steps

Create a module that will have a date and time field
Go to all records and click on add records
When you are adding the record, click on the date
When the calendar is opened, try to resize your browser or use it as a split screen and notice that the calendar is cutted out.

Expected behavior
The calendar should be shown fully.
Screenshot/Video

https://user-images.githubusercontent.com/53232926/224648108-c168ab18-31f2-43fe-b0c5-f96f6f6eea20.webm
Version
20233-qc.cortezaproject.org
My screen is 16" (2560x1600)

This issue is the same on Public pages with record lists. It isn't obvious because of the layout difference there.

For today: Continue to find a fix for this issue

For today: continue investigating the cause of the issue and sync with Jože to discuss whether to continue work on this task or prioritize other tasks

Tested and confirming that this now works as intended. CL entry is not needed here since this is a fix for 2023.

authors: Bojan-Svirkov EmmyMay katrinDY

repo: cortezaproject/corteza


text:
updated readme about node v7 harmong_proxies flag issue

#366

Coverage remained the same at 95.283% when pulling 23c71e9f972bf46a779110dd6e2ae872204b3ce0 on arshdkhn1:readme-update into 565a482d1a1b6ea495593ebb5749eaa8b9be1466 on coryhouse:master.

@coryhouse Do you agree to say that it is not supported? If so, I believe we should also update the nodeVersionCheck.js

I'd suggest just mentioning changing the test script if using Node 7. It's otherwise supported, right?

Agreed. I think the line in the PR makes it sound completely unsupported where only that flag within that script is unsupported.
It may make sense to put a warning in the nodeVersionCheck and not an error to help inform users of the unsupported flag.

Closing since handled via #368

authors: arshdkhn1 coryhouse coveralls kwelch

repo: coryhouse/react-slingshot

license: mit


text:
_makeOAuthCall is not working

In the method the _makeOAuthCall, The cURL return josn data  displays the  error  message  like :  {"code": 400, "error_type": "OAuthException", "error_message": "Invalid Client Secret"}

Is there anyone to help me out??

I need an urgent help.

you gotta enter corect client secret

Despite entering correct client secret, it shows the error.

authors: Suba-Sah dsslimshaddy

repo: cosenary/Instagram-PHP-API


text:
Move bottom sheet info to floating card

This PR moves the bottom sheet into a floating card.

This can be merged once checks have all passed.

Actually, I've been looking at this a bit more closely while waiting for the checks to not pass, and it looks like there are some issues with the gif-play-pause component.
It's complaining about a missing "paused" prop. Making the prop true makes the icon disappear (so there's a blank white circle). Ideally, this would be paused to start with, but I can't figure out how to do that.
[Vue warn]: Missing required prop: "paused"
  at <GifPlayPause gif="img/eclipse.471bc4cb.gif" still="img/eclipse_static.9b273521.gif" alt="Cartoon of a Solar Eclipse" >

authors: johnarban patudom

repo: cosmicds/minids


text:
Need to recreate yarn.lock with newest dependencies

if we recreate yarn.lock atm, we'll run into trouble with module ast and telescope(ofc). Versioning of some packages are not compatible with each others (e.g: @babel/types, ...)
Resolve the dependencies and create a new yarn.lock.

fixed in commit 9d5071

repo: cosmology-tech/telescope


text:
Upgrade yarn to version 3

See https://dev.to/arcanis/yarn-3-0-performances-esbuild-better-patches-e07
Should fix
### Maybe don’t use Node v15+ until you upgrade to Yarn v3(!!!)

It might not affect you but there’s an issue with the `fs` patch and `bigint`,
which is solved in v3, but won’t be backported to v2:
https://github.com/yarnpkg/berry/issues/2232#issuecomment-818514929

from https://github.com/cosmos/cosmjs/blob/v0.26.1/docs/YARN.md

So.... v2 still has limited support and they move to v3 already? oof.

v3 is the better v2. No huge difference. If you are interested, see the blog artice. It's interesting and shows there was a huge change between v1 and v2 and now it gets smoother. The article also addresses some frustration of users.

repo: cosmos/cosmjs


text:
Fix some broken links in whitepaper

Mostly for the historical record.

Hi @mveytsman  kindly visit the official COSMOS page to start a chat with an official agent on alive chat support to report this for review and for further assistance via LIVE CHAT

repo: cosmos/cosmos


text:
Create ibc-go documentation website

Summary
I added the basic necessities to build locally the ibc-go website in #146. It could use some prettyness work but the main missing component is the logo in the corner
Now we just need to deploy it and ideally integrate its deployment into our github actions. I'm not sure how to handle this part
@okwme do you know who could help deploying this? I was thinking of using the ibc.cosmos.network domain

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged/assigned

pinging @marbar3778 and @lovincyrus to confirm. I believe it can be deployed with netlify if it needs a build script (and routing) or github pages if it's just markdown files. Either way we can set up CNAMEs to use a subdomain. I like ibc.cosmos.network but there's also the option of using the ibcprotocol.org website like docs.ibcprocol.org.

I think we can close this! http://ibc.cosmos.network/main/ibc/overview.html

authors: colin-axner okwme

repo: cosmos/ibc-go


text:
e2e: v8.1 upgrade test

Description

closes: #5635

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against the correct branch (see CONTRIBUTING.md).
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards and Go style guide.
[ ] Wrote unit and integration tests.
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/).
[ ] Added relevant godoc comments.
[ ] Provide a commit message to be used for the changelog entry in the PR description for review.
[ ] Re-reviewed Files changed in the Github PR explorer.
[ ] Review Codecov Report in the comment section below once CI passes.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (6174822) 81.16% compared to head (c1c8955) 81.16%.
Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5652   +/-   ##
=======================================
  Coverage   81.16%   81.16%
=======================================
  Files         198      199    +1
  Lines       15267    15278   +11
=======================================
+ Hits        12392    12401    +9
- Misses       2407     2408    +1
- Partials      468      469    +1

see 2 files with indirect coverage changes

authors: codecov-commenter damiannolan


text:
Update CHANGELOG.md

Thank you a lot for contributing to Cosmos Voyager!

Issue

closes: ISSUE
Screenshots

❤ Thank you!

was just to test

repo: cosmos/voyager


text:
Conan package

Hello,
Do you know about Conan?
Conan is modern dependency manager for C++. And will be great if your library will be available via package manager for other developers.
Here you can find example, how you can create package for the library.
If you have any questions, just ask :-)

I'm closing this issue for now.
We will consider supporting Conan when users request it, however you are most welcome to create a Conan package.
Thank you

repo: cossacklabs/themis


text:
RustThemis

It's hard to use Themis from programs in Rust without bindings. Let's fix this.

[x] Move source from rust-themis into this repo
[x] No really, move it and archive the old repo
[x] Integrate Rust builds into Makefile
[x] Integrate Rust builds into CircleCI
[x] Integrate Rust binding into cross-language tests
[x] Add CircleCI badges to crates.io READMEs
[x] Make API documentation available (on docs.rs or elsewhere)
[x] Move API docs to a more official Cossack Labs domain (docs live on docs.rs now)
[x] Write a language guide for Rust on wiki
[x] Update links in the language guide
[x] Update the top-level README and Wiki pages to declare Rust support

Almost there! 🏁

We did it! 🎉


text:
🛑 Mainnet Smartpy is down

In 4ae362d, Mainnet Smartpy (https://mainnet.smartpy.io/chains/main/blocks/head/header) was down:

HTTP code: 502
Response time: 215 ms

Resolved: Mainnet Smartpy is back up in 248a1e1.

repo: cotezos/teznodes