Tags: attackgithub/clouddriver
Tags
feat(clouddriver-bom): publish clouddriver-bom (spinnaker#3794) This simplifies dependency resolution downstream
fix(snapshots): ignore not found in delete operation (spinnaker#3793)
fix(ecs): If in "host" network mode, host and container port should b… …e the same (spinnaker#3776) (spinnaker#3791)
fix(ecs): Don't specify load balancer role for non-load-balanced serv… …ice (spinnaker#3740) (spinnaker#3759) Fixes spinnaker/spinnaker#4475
Revert "chore(clouddriver/oracle): Get the Oracle API jar from Maven. (… …spinnaker#3695)" (spinnaker#3756) This reverts commit 6a1be53.
fix(cf): remove sensitive information from credentials payload (spinn… …aker#3752) (spinnaker#3754)
perf(kubernetes): Reduce memory allocation during caching cycles (spi… …nnaker#3736) (spinnaker#3746) * perf(kubernetes): Reduce memory allocation during caching cycles The caching logic for the kubernetes v2 provider allocates a lot of short-term memory during each caching cycle, putting pressure on the garbage collector, in some cases exceeding the garbage collection overhead. A significant contributor is the logic to compute relationships between kubernetes objects. We currently create a CacheData object to hold each relationship and rely on downstream (and inefficient) logic to merge these into one CacheData per object, containing all of its relationships. Improve this by having invertRelationships return one CacheData per object (containing all of its relationships) rather than on CacheData per relationship. Likewise, have getClusterRelationships return a single CacheData for each application, rather than a separate one for each application-object relationship. * test(kubernetes): Add tests to getClusterRelationships Also simplify the logic in the invertRelationships test
PreviousNext