March logbook

2023-03-28

• added AWS cert to dev plan

• OAuth & Skipper discussion with FG

  • two facets, first CEIP-3114 Security Vulnerability: CORTEX cluster all management services are… https://opensource.zalando.com/skipper/tutorials/auth/#openid-connect
  • second: training scope

• training scope

  • publish to artifactory check Makefile from cortex-operations for publication to artifactory request repository in artifactory via tech desk
  • could do anonymous read but might be the wrong thing

2023-03-27

• investigate cortex-warnings resulting in:
  • https://elsevier.atlassian.net/browse/CEIP-3532: Raise CPU limit on twistlock in core-platform-manager
• inspector and planning meetings

2023-03-23

• training
  • audit #cortex-help
  • create static site container
• add sonarqube to crtxctl? https://backstage.elsevier.net/docs/default/component/core-cicd-reference/github-actions/getting-started/adding-sonarqube/

2023-03-22

• 1-2-1
  • Hack day
  • BPM for self service
  • KNative
  • How make the most of Cortex?
    • track resource use (aka cost)
    • be good neighbour
• prep:
  • talent sheet
  • OKRs
    • training
      • scope: 101: intro to Cortex: basic summary of docs 102: troubleshooting with Inspector
  • Dev plan
• NR training

2023-03-22

• half a dozen small doc changes
• prep:
  • talent sheet
  • OKRs
  • Dev plan

2023-03-21

• skipper blue green

  • delete kube-web-view does not remove service if deployment delete (does if helm uninstall)

  • copy inputs for kube-web-view from platform defs (inc. enable ingress)

  • install helm upgrade --install kube-web-view-20230321 . -n kube-system -f values-blue-green.yaml

  • that gets the ingress up but pod is now unhealthy (shown in describe events not on get) Warning Unhealthy 2m kubelet Readiness probe failed: Get "http://100.67.107.22:8080/health": dial tcp 100.67.107.22:8080: connect: connection refused

  • No further event added but after a short wait the endpoint is available

  • Next try adding additional annotations for blue green

  • added annotation to new ingress and removed old

  • new ingress routes consistently to new pod

  • restart pod

  • no difference, had wrong syntax on annotation

  • cannot feed necessary spec into chart (which makes sense as seeking to link two services from diff installs)

  • install ``

2023-03-20

• dev duty
• bug fix crtxctl
• retro & planning
  • candidate for me (or Khush): https://elsevier.atlassian.net/browse/CEIP-3341
  • search planning for JFDI docs
• green-blue skipper doc

2023-03-17

• Cannot reset password (again!). Ticket: Inc-1366934
• 1-2-1
  • record sick from 13-16 inc.
  • OKRs
    • Documentation and Training
    • BPM engine for self-service
    • cert K8s admin: https://training.linuxfoundation.org/certification/certified-kubernetes-administrator-cka/
    • Fully managed service offering (KNative?)
• Read platform warnings blog
• Finish vale GHA
• NPS

2023-03-09

• NPS
  • single number
  • good text
  • bad text
  • procedure
• vale GitHub action
• couple hours out due to mind fog
• identity conversation
• troubleshoot crtxctl w AN

2023-03-08

• NPS discussion
• Inspector as lambda, tickets to follow
• small additions to ops site (menu and scrolling toc)
• CEIP-2721: mothball old calculator

2023-03-07

• Twistlock

  • in the beginning…
  • twistlock by account or by namespace

• Docs updates w CB and SB

• command pattern for crtxctl

• more twistlock (impl side via Terraform)

2023-03-06

• NPS opportunity: time from merge to pending to running (or failed)
  • TV has compared running to failed.

2023-03-03

1-2-1 Completing troubleshoot PoC Liasied

2023-03-02

• New Relic chart repo in platform.yaml points to which is redirecting to https://newrelic.github.io/helm-charts/, but unfortunately that is returning 404!

2023-03-01 - Office day

Release process

• new Cortex confluence space for heads of BU, mgmt

• Roadmap process?

• NPS: reads of blog posts

• Need requirement from partner on response time to GitOps merge

• GitHub user must = Partner inc. Product not just TIO

• IP: exclude Alpha from release (as lab environment)

  • Partners ‘donate’ an alpha cluster for us to validate their needs
  • Advice for HM: May need alpha if developers would be blocked by beta outage (so can try TIO stuff)
  • Note that testing occurs in branch so release process does not occur.

• Build release: https://github.com/elsevier-centraltechnology/cortex-platform-manager/blob/documentation-review/CICD.md