eirini-release
eirini-release copied to clipboard
cloudfoundry
Helm release for Project Eirini
https://www.cloudfoundry.org/projects/#application_runtime_pmc-subproject-eirini the project site link for eirini needs to be removed as it appears the domain has been picked up by some unsavory folks. Didn’t really know where to address...
Our hack script invokes two scripts: - vendor/k8s.io/code-generator/generate-groups.sh, which generates - the deepcopy functions - the versioned client - listers - informers - vendor/sigs.k8s.io/controller-tools/cmd/controller-gen, which generates - CRDs Kubebuilder only...
`eirini-controller` should expose health endpoints as described [here](https://kubernetes.io/docs/reference/using-api/health-checks/). According to that document, `healthz` is deprecated in favour of `livez` and `readyz`, so we should have: * two endpoints, one for...
The following fields in `eiriniv1.LRP` and `eiriniv1.Tasl` act only as metadata (they get converted to labels): - `GUID` - `Version` - `Name` - `ProcessType` - `App/Space/OrgName/GUID` Fields like `GUID`, `Name`...
The following fields in `eiriniv1.LRP` act only as metadata (they get converted to labels), so we should remove them: - `GUID` - `Version` - `ProcessType` - `App/Space/OrgName/GUID` `GUID` and `Version`...
Let's group these three related fields.
Let's group these three related fields.
The following fields in `eiriniv1.Task` act only as metadata (they get converted to labels), so we should remove them: - `GUID` - `Name` - `App/Space/OrgName/GUID` `GUID` and `Name` are replaced...
Nothing is logged when a Task is cancelled. Instead, it would be nice to log something like this: ``` {"timestamp":"...","level":"info","source":"api","message":"cancel-task.started","data":{"session":"218"}} {"timestamp":"...","level":"info","source":"api","message":"cancel-task.listing-jobs","data":{"session":"218", "label-selector": "..."}} {"timestamp":"...","level":"info","source":"api","message":"cancel-task.deleting-job","data":{"session":"218", ...}} {"timestamp":"...","level":"info","source":"api","message":"cancel-task.ended","data":{"session":"218", "response-code": 200}} ``` Let's...
Nothing is logged when the details of a Task are requested. Instead, it would be nice to log something like this: ``` {"timestamp":"...","level":"info","source":"api","message":"get-task.started","data":{"session":"218"}} {"timestamp":"...","level":"info","source":"api","message":"get-task.listing-jobs","data":{"session":"218", "label-selector": "..."}} {"timestamp":"...","level":"info","source":"api","message":"get-task.ended","data":{"session":"218", "response-code": 200}} ```...