-
Notifications
You must be signed in to change notification settings - Fork 46
Milestones
List view
1.34 upgrade for kubernetes
No due date•1/17 issues closedRun the chosen Gateway API implementation in parallel with Nginx Ingress on CP2, allowing some early adoption/testing for the CP3 version and as a potential backup plan for CP2.
No due date•1/4 issues closedA minimally specced set of features to permit some selected workloads for existing CP2 tenants to deploy a pre-production version of an appliaction into CP30, using as much as the existing user-facing CP2 technology as possible, (Helm, GitHub Actions, Circle CI, GHCR, etc.) excludes: ArgoCD, mTLS, no EBS/PV, etc., 'stateful' resources in CP3/MP, no CP3 AWS services, etc. includes: GatewayAPI, 'stateful' resources will be in existing CP2 account, Envoy, DNS & TLS Certificate Management, EIPs on Load Balancers optional: private EKS API, ...
Overdue by 9 day(s)•Due by July 8, 2026•6/15 issues closed- Overdue by 22 day(s)•Due by June 25, 2026•5/18 issues closed
- No due date•0/2 issues closed
- No due date•0/2 issues closed
- No due date•6/10 issues closed
- No due date•1/1 issues closed
- No due date•0/20 issues closed
- No due date•11/27 issues closed
- No due date•0/16 issues closed
- No due date•0/6 issues closed
- No due date•0/3 issues closed
- No due date•0/2 issues closed
- No due date•2/21 issues closed
- No due date•18/18 issues closed
Deploy cluster to rest of accounts Ensure end to end deployment from development onwards Storage add-ons
No due date•9/10 issues closedExclusively for platform engineers, not for user accounts
Overdue by 6 month(s)•Due by January 14, 2026•3/3 issues closedCapabilities required to Bootstrap a v3.0 Platform in our new MP accounts and to enable CloudPlatform Engineers to Develop the Platform.
Overdue by 6 month(s)•Due by January 14, 2026•8/8 issues closedStart using provided CIDR ranges allocated to CP3 VPC Endpoints for AWS Services Connectivity to MOJ Transit Gateway to able to access wider network Logs to SOC (although most are going over the internet)
Overdue by 4 month(s)•Due by February 27, 2026•43/44 issues closedWe had to pause Kraken in Sept/Oct 2025. This milestone is to look at what a replacement may look like.
Overdue by 17 day(s)•Due by June 30, 2026•1/1 issues closed1.33 upgrade for kubernetes
No due date•16/17 issues closed- No due date•13/14 issues closed
This milestone captures all low volume VPC Endpoint interfaces/gateways for bringing access to all Cloud Platform AWS services internally.
Overdue by 5 month(s)•Due by January 31, 2026This milestone captures all VPC Endpoint interfaces/gateways for bringing access to all Cloud Platform AWS services internally. It includes those Endpoints with medium usage.
Overdue by 6 month(s)•Due by December 31, 2025- No due date•2/2 issues closed
Remove all Ruby code and replace with Go
No due date•6/6 issues closed- No due date•1/1 issues closed
This milestone captures all Initial work going towards implementing VPC Endpoint interfaces/gateways for bringing access to all Cloud Platform AWS services internally. It includes those Endpoints with high usage.
Overdue by 7 month(s)•Due by December 4, 2025•5/5 issues closedlive-2 doesn't offer that much additional value than test clusters, but comes with additional maintenance overhead. If we can improve test clusters to cover the value gap we can delete live-2
No due date•2/2 issues closed- Overdue by 9 month(s)•Due by September 24, 2025
Updates on how RDS Snapshots are managed
No due date•3/3 issues closedHigh-level milestone. Items will be broken down into smaller packages of work.
No due date•15/15 issues closedHigh-level milestone. Items will be covered by 'Networking' but should be worked in smaller sub-categories
No due date•9/9 issues closedThis is a high-level milestone that covers dev or enhancement of general user features. These are likely to be worked individually and not as a group of items.
No due date•19/19 issues closedHigh-level milestone. Items will probably be broken down into smaller packages of work
No due date•4/4 issues closedThis is a high-level milestone, however given the topic I would expect items to be worked on as individual tickets rather then grouped and worked on in bulk.
No due date•10/10 issues closedThis is a high-level milestone. Items within my be broken down in to smaller sub-category of items.
No due date•17/17 issues closedThis is a high-level milestone/category. Items should be broken down into smaller sub-categories or topics of work
No due date•33/36 issues closed- No due date•9/9 issues closed
- No due date•10/10 issues closed
This milestone is to capture the ticket required to ensure all Cloud Platform AWS resources are tagged to FinOps requirement. MoJ Tagging Reference: https://technical-guidance.service.justice.gov.uk/documentation/standards/documenting-infrastructure-owners.html#mandatory
Overdue by 10 month(s)•Due by August 27, 2025•38/38 issues closed- No due date•3/3 issues closed
We want to be able to upgrade on a new cluster and transfer traffic across in a controlled way, to reduce the risk and time it takes to upgrade clusters. https://aws.amazon.com/blogs/containers/blue-green-or-canary-amazon-eks-clusters-migration-for-stateless-argocd-workloads/ https://aws-ia.github.io/terraform-aws-eks-blueprints/patterns/blue-green-upgrade/
No due date•7/7 issues closedThis is a container for all tickets relating to the decommissioning of git-crypt in favour of a safer, more modern and programmatic approach for managing all of our tfvars encrypted secrets.
No due date•4/4 issues closedAllow more user (PRs) to be auto-approved without manual involvement of CP engineers.
Overdue by 11 month(s)•Due by August 13, 2025•6/6 issues closedWork to push the platform logs to the SOC team for them to analyse them and raise any findings with us. Cloud Trail Logs, Network flow logs, Route53 logs, EKS logs.
Overdue by 11 month(s)•Due by August 13, 2025•8/8 issues closed- No due date•13/13 issues closed
- No due date•6/6 issues closed
Bring the how-out-of-date-are-we reports up to date moving from ruby to go, fix the problem with the DynmoDB size issues and consolidate the app cron onto one cluster, removing cronjobs from concourse-main
No due date•9/9 issues closed