Chris Stanaway

Results 10 issues of Chris Stanaway

Using image 3.1.0. Created scenario: ``` apiVersion: powerfulseal.io/v1 kind: Scenario metadata: name: default-node-death namespace: kube-system spec: name: default-node-death description: "default nodegroup: kill a single node" steps: - nodeAction: matches: -...

Running 2.9.1 (yes, I know, it's old). We have several different clusters, but don't have the same k8s deployments in each cluster. Tried to use a generic policy definition. When...

help wanted
good first issue
hacktoberfest

Various places (docs, deployment manifest) refer to image `powerfulseal/powerfulseal:3.1.1`. However, this image does not appear to exist. There are no images tagged at https://hub.docker.com/_/powerfulseal. The most recent image that appears...

With PowerfulSeal 3.1.0: ``` $ curl http://localhost:8001/api/v1/namespaces/kube-system/pods/powerfulseal-85f968c9d9-tsmjj:9090/proxy/metrics # HELP process_virtual_memory_bytes Virtual memory size in bytes. # TYPE process_virtual_memory_bytes gauge process_virtual_memory_bytes 355807232.0 # HELP process_resident_memory_bytes Resident memory size in bytes. #...

When run with `--inventory-kubernetes` does seal collect the set of nodes only at startup or at the start of each "run" (when in autonomous mode)? I'm really hoping it refreshes...

The CRD specification at `https://github.com/powerfulseal/powerfulseal/blob/master/kubernetes/crd.yml` does not include the `stopPodsHostAction`. Thus any scenario defined via a CRD which attempts to include the `stopPodsHostAction` action is rejected.

**Is your feature request related to a problem? Please describe.** No **Describe the solution you'd like** Within a scenario, a schedule can be defined as part of the filter section....

I'm running a simple test with 3 masters + 1 slave per master. If I take down one of the slaves and restart it, ioredis fails to reconnect to that...

pinned

Any chance that this will be updated to support OpenAPI 3.0? This new version of the Swagger specification was released in July 2017.

**Which component are you using?**: vertical-pod-autoscaler **What version of the component are you using?**: Component version: 0.12.0 **What k8s version are you using (`kubectl version`)?**: kubectl version Output $ kubectl...

vertical-pod-autoscaler
kind/bug