Netflix/chaosmonkey

chaosmonkey can not kill kubernetes v2 resource in spinnaker

Open

#60 opened on Aug 6, 2019

View on GitHub
 (6 comments) (0 reactions) (0 assignees)Go (9,318 stars) (688 forks)batch import
enhancementhelp wanted

Description

when we use Kubernetes Provider V2 (Manifest Based), chaosmonkey can not find resource to kill, Name 'ingress service-xxx' does not have any labeled or unlabeled matches. No eligible instances in group, nothing to terminate

some issue in here: https://github.com/spinnaker/spinnaker/issues/3929

example msg:

chaosmonkey config testclient
(*chaosmonkey.AppConfig)(0xc820332240)({
 Enabled: (bool) true,
 RegionsAreIndependent: (bool) true,
 MeanTimeBetweenKillsInWorkDays: (int) 2,
 MinTimeBetweenKillsInWorkDays: (int) 1,
 Grouping: (chaosmonkey.Group) cluster,
 Exceptions: ([]chaosmonkey.Exception) {
 },
 Whitelist: (*[]chaosmonkey.Exception)(<nil>)
})

error msg:

chaosmonkey terminate  testclient infra-k8s-hk`

[ 7452] 2019/07/30 07:38:42 WARNING: eligible.Instances failed for InstanceGroup{app=testclient account=infra-k8s-hk region= stack= cluster=}: Name 'deployment nginx' does not have any labeled or unlabeled matches

[ 7452] 2019/07/30 07:38:42 No eligible instances in group, nothing to terminate: InstanceGroup{app=testclient account=infra-k8s-hk region= stack= cluster=}

image

Contributor guide

Tech stack
gokubernetes
Domain
infrastructureclouddevops
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Go programmingKubernetes basicsChaos Monkey concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Investigate how Chaos Monkey discovers instances in Kubernetes v1 vs v2. Look at the `eligible.Instances` function and the resource matching logic, likely in files related to Kubernetes provider. Check linked issue #3929 for more context. Ensure that the naming convention for v2 resources (deployments, services) is properly handled.