peer library application
chilldude/peer-library-frontend 3
frontend code for peer library platform
.dotfiles/setup.sh to set up a fresh puter
Internal API to access the database for Diego.
Command line utility for standing up a BOSH director on an IAAS of your choice.
BOSH CLI v2
Collection of BOSH manifests referenced by cloudfoundry/docs-bosh
cwlbraa/bosh-io-release-resource 0
tracks BOSH releases published on https://bosh.io
A go package for the V2 CF Service Broker API
CF Acceptance tests
push eventcloudfoundry/capi-k8s-release
commit sha 00fe7fd5eb9aad9f758ba94f4b8e36ae84f4375c
remove eirini cert defaults (#68) - requires https://github.com/cloudfoundry/cf-for-k8s/pull/425 [finishes #174720931] Authored-by: Connor Braa <[email protected]>
push time in 15 hours
PR merged cloudfoundry/capi-k8s-release
these are not necessary.
requires https://github.com/cloudfoundry/cf-for-k8s/pull/425
pr closed time in 15 hours
pull request commentcloudfoundry/capi-k8s-release
refactor config loading / validation in cf-api-controllers
LGTM! I appreciate that this sets us up pretty well to use a configmap in the future if we want.
comment created time in 16 hours
push eventcloudfoundry/capi-k8s-release
commit sha b0f1d47a84f5647321c57792a597a45a683fd731
temporarily override ccng start command until procfile fix comes through Authored-by: Connor Braa <[email protected]>
push time in 17 hours
push eventcloudfoundry/cloud_controller_ng
commit sha 6857230592e76dc067e442ab52aabfc1065727bf
add secrets flag to web process in ccng procfile Authored-by: Connor Braa <[email protected]>
push time in 18 hours
push eventcloudfoundry/capi-dockerfiles
commit sha b81c3ef2ef2839c1a341e6ddd725d70226c32ccc
update pack version in CI to 0.13.1 - older version didn't have process type symlinks [#174523162] Co-authored-by: Connor Braa <[email protected]> Co-authored-by: Piyali Banerjee <[email protected]>
push time in 18 hours
issue commentcloudfoundry/cloud_controller_ng
Unable to see list of detected CNBs for apps build by kpack
I think this doesn't work regardless of whether you specify a buildpack, and it likely should work with no buildpack specified.
comment created time in 19 hours
push eventcloudfoundry/capi-ci
commit sha 7bb919efcb5e0610364a6e9a36abcf9ec63ba054
use newer builder to build ccng image [#174523162] Co-authored-by: Connor Braa <[email protected]> Co-authored-by: Piyali Banerjee <[email protected]>
push time in a day
push eventcloudfoundry/capi-k8s-release
commit sha 5d60a61e9a23734027cc369643a498890fa8b5ad
Build CCNG image with paketo buildpacks - Configure our dev scripts to build it using `pack` - Update nginx Dockerfile to support the users/groups to match CNB ones that the buildpacks create - Stop running package-image-uploader container as root Co-authored-by: Connor Braa <[email protected]> Co-authored-by: Jaskanwal Pawar <[email protected]> [finishes #174653760]
push time in 2 days
push eventcloudfoundry/capi-ci
commit sha a6fc9806fe0b202ae41fbf3b4433900cbc803cfc
build ccng with pack in CI Co-authored-by: Connor Braa <[email protected]> Co-authored-by: Piyali Banerjee <[email protected]>
push time in 2 days
push eventcloudfoundry/capi-ci
commit sha 3c413cec1a7b5abf3d4266a2430cea3504654715
build ccng image with pack [#174523162] Co-authored-by: Connor Braa <[email protected]> Co-authored-by: Piyali Banerjee <[email protected]>
push time in 2 days
push eventcloudfoundry/cloud_controller_ng
commit sha 486618225c1c9f8f68a2741fd7b689c0df92a08a
fixes to make ccng buildable with ruby cnb [#174523162]
push time in 2 days
push eventcloudfoundry/capi-k8s-release
commit sha 19ce1389484e4da87083d6b2954dfe5ad687cc88
Set memory and cpu requests and limit values for all containers (#65) * Set memory and cpu requests and limit values for all containers [#174462927](https://www.pivotaltracker.com/story/show/174462927) Co-authored-by: Paul Warren <[email protected]> * ENH: Increase worker, clock, and deployment updater requests and limits to 300m/1000m, as requested [#174559282](https://www.pivotaltracker.com/story/show/174559282) [finishes #174559282] Co-authored-by: Eric Promislow <[email protected]> Co-authored-by: Angela Chin <[email protected]> Co-authored-by: James Pollard <[email protected]> Co-authored-by: Eric Promislow <[email protected]>
push time in 3 days
PR merged cloudfoundry/capi-k8s-release
Relint is currently working on a scaling and Quality of Service (QoS) set of stories.
We are targeting 1.0 to be configured out-of-the-box as a "developer" edition aimed at those users who want to kick the tyres. As part of this, we would like to set limits on mem/cpu.
Since a "developer" edition may not be preferred by everyone, we want each component to be configurable to scale both horizontally (replicas) and vertically (mem/cpu). This will also allow users to deliver a Guaranteed QoS when required (although we are recommending that all of our pods and containers use the Burstable QoS) As part of this we would like to ask you to do several things:
- consider which of your pods/containers you would like to expose for scaling properties for.
- expose said configuration properties.
- sets mem and cpu values for all containers in order to provide as much meta-data to k8s as possible so that its scheduler can do as good a job as possible. This PR is an initial attempt at setting these values, although we know you are much more likely to have insight into your components mem/cpu requirements than our guess.
If you have any questions or concerns, please let us know! Thanks!
Co-Authored-By: Angela Chin [email protected]
pr closed time in 3 days
push eventcloudfoundry/cloud_controller_ng
commit sha 6a957c3927439732ed89a53448d2aee038231123
clean up some left over merge cruft in manifests_specs * there was a commented out test in space_manifests_spec that slipped through in a big squash * reimplemented the same test in app_manifests_spec Authored-by: Connor Braa <[email protected]>
push time in 4 days
Pull request review commentcloudfoundry/cloud_controller_ng
emit pending/failed job metrics even when queue is empty
def update_job_queue_length total = 0 pending_job_count_by_queue = jobs_by_queue_with_count.each_with_object({}) do |row, hash|+ @known_job_queues[row[:queue].to_sym] = 0 total += row[:count] hash[row[:queue].to_sym] = row[:count] end + pending_job_count_by_queue = @known_job_queues.merge(pending_job_count_by_queue)
reverse_merge! is best IMO, it disambiguates the structure of of the final hash and shows that the transformation is being done in-place.
comment created time in 4 days
issue closedcloudfoundry/cloud_controller_ng
cf4k8s: POST /v3/builds gives a weird error message
Thanks for submitting an issue to cloud_controller_ng. We are always trying to improve! To help us, please fill out the following template.
Issue
Creating a package failed with an unexpected error message
Context
We're exploring how much of CATs will be runnable on cf4k8s
Steps to Reproduce
Focus https://github.com/cloudfoundry/cf-acceptance-tests/blob/7f4027c7a0b2c00f8e56a6d40904b8f65b4ed485/v3/deployment.go#L84
Modify https://github.com/cloudfoundry/cf-acceptance-tests/blob/7f4027c7a0b2c00f8e56a6d40904b8f65b4ed485/helpers/v3_helpers/v3.go#L412 to not specify a list of buildpacks when no buildpacks are passed in
Expected result
We were hoping this would just work
Current result
We got this error:
"errors": [
{
"detail": "Package guid can't be blank, Package guid must be a string, Package guid must be between 1 and 200 characters, Lifecycle data must be an object",
"title": "CF-UnprocessableEntity",
"code": 10008
}
]
Pertinent logs:
\"backtrace\"=>[\"/cloud_controller_ng/app/controllers/v3/application_controller.rb:18:in
`unprocessable!'\",
\"/cloud_controller_ng/app/controllers/v3/builds_controller.rb:32:in
`create'\",
closed time in 5 days
ericpromislow
push eventcloudfoundry/capi-k8s-release
commit sha 4df1a8b37d933c2faeabefef5147d3ae0eac71eb
fix image_changed helper to actually return exit code Authored-by: Connor Braa <[email protected]>
push time in 5 days
Pull request review commentcloudfoundry/cloud_controller_ng
emit pending/failed job metrics even when queue is empty
def update_job_queue_length total = 0 pending_job_count_by_queue = jobs_by_queue_with_count.each_with_object({}) do |row, hash|+ @known_job_queues[row[:queue].to_sym] = 0 total += row[:count] hash[row[:queue].to_sym] = row[:count] end + pending_job_count_by_queue = @known_job_queues.merge(pending_job_count_by_queue)
the name makes this opaque to me... before doing this merge pending_job_count_by_queue is different how? what do we accomplish by merging them?
comment created time in 5 days
push eventcloudfoundry/capi-k8s-release
commit sha 0f2a80b51bc5680d5399c31f11eef8e93852eb7a
make sure shortlog script is in capi-k8s-release when running "git log" Authored-by: Connor Braa <[email protected]>
push time in 5 days
push eventcloudfoundry/capi-ci
commit sha 91314abc0082c4bda60f01bc70159335911a65c9
execute shortlog script from parent directory so paths can be relative Authored-by: Connor Braa <[email protected]>
push time in 5 days
push eventcloudfoundry/capi-bara-tests
commit sha 5f644af36a1c82c2e60842c75e84a4d383283558
extend stack droplet eventually timeout - it flaked in https://capi.ci.cf-app.com/teams/main/pipelines/capi/jobs/samus-cf-for-k8s/builds/1236 Authored-by: Connor Braa <[email protected]>
push time in 5 days
push eventcloudfoundry/cloud_controller_ng
commit sha 3946106f3508f64f2ddb1898faf870cea23b4513
add error on cf-for-k8s when type: buildpack is configured this error is conditional on default_app_lifecycle for now as its the most closely associated config field currently available. it might be surprising to find that setting a default_app_lifecycle excludes the opposite one. in the future we should consider an explicit field about which lifecycles are supported OR find a way to support the user asking for either when the other is not present. [finishes #174224146] Authored-by: Connor Braa <[email protected]>
push time in 5 days
issue commentcloudfoundry/cloud_controller_ng
cf4k8s: POST /v3/builds gives a weird error message
when trying to repro, I found that this bug doesn't exist in this exact form any more. There is a similar class of errors that occur when a cf-for-k8s CC tries to handle build requests with "lifecycle":{ "type": "buildpack" }. To mitigate that, I'm adding some validation that will error if the default app lifecycle is kpack but a user requests a buildpack lifecycle.
the new, undesirable errors look roughly like this:
cf curl /v3/builds -X POST -d {"lifecycle":{ "type": "buildpack", "data": { "buildpacks": ["paketo-community/ruby"] } }, "package": { "guid" : "3516e484-e4bc-4e57-adcd-1f6c873f3fa0"}}
{
"errors": [
{
"detail": "Buildpack \"paketo-community/ruby\" must be an existing admin buildpack or a valid git URI",
"title": "CF-UnprocessableEntity",
"code": 10008
}
]
}
the new ones should look roughly like:
{
> "errors": [
> {
> "detail": "this installation does not support the "buildpack" lifecycle, try "kpack" instead",
> "title": "CF-UnprocessableEntity",
> "code": 10008
> }
comment created time in 5 days
issue commentcloudfoundry/cloud_controller_ng
cf4k8s: POST /v3/builds gives a weird error message
plan:
- [ ] follow repro instructions
- [ ] make lifecycle: buildpack invalid on cf-for-k8s (it never works anyways)
- [ ] investigate space_manifests_spec test cruft
comment created time in 5 days
push eventcloudfoundry/capi-ci
commit sha 253044b30f375b0694882433be13dd4ad3e31157
export _DIR vars when bumping capi-k8s-release image references - this is so the capi-k8s-release script can pick ccng up from the correct location Authored-by: Connor Braa <[email protected]>
push time in 5 days
push eventcloudfoundry/capi-k8s-release
commit sha 575ae64fc3795cbdfb04f8bdafcf860067f1fa7a
remove colons from github links in shortlog script Authored-by: Connor Braa <[email protected]>
push time in 8 days
push eventcloudfoundry/capi-ci
commit sha 5dcc4e70ceb846a8756ecbd1d635631cccb28920
remove -x debug Authored-by: Connor Braa <[email protected]>
push time in 8 days
push eventcloudfoundry/capi-ci
commit sha 145ef92d20d0d221dd1275e98d07526dc17ff4f3
set -x to debug bump script Authored-by: Connor Braa <[email protected]>
push time in 8 days
push eventcloudfoundry/capi-k8s-release
commit sha e4b33d1172b4de7f53bcbc20dbb0cf59a2b320c8
inline unnecessary variable in shortlog script Authored-by: Connor Braa <[email protected]>
push time in 8 days
push eventcloudfoundry/capi-k8s-release
commit sha d00515fb994603fb74848dde21cafd62fc43ac9f
add links to generated shortlog Authored-by: Connor Braa <[email protected]>
push time in 8 days
push eventcloudfoundry/capi-ci
commit sha 5b4a505913f84f72a54c4dd49b281bf2ec2da012
use new shortlog script in CI Authored-by: Connor Braa <[email protected]>
push time in 8 days
push eventcloudfoundry/capi-k8s-release
commit sha 05aceaa6e30bfa6f7917d1ff1225f2d2b061217d
inline commit message for shortlog Authored-by: Connor Braa <[email protected]>
push time in 8 days
push eventcloudfoundry/capi-k8s-release
commit sha a4f5823c54dec9b713ece05141bb4ef7b35fd630
remove unnecessary kbld parameter Authored-by: Connor Braa <[email protected]>
commit sha 8e45b675c060e0d9fb8a0b06dacb3e17c1ade468
improved shortlog script - only notes when there are changes from the last recorded image - more machine parsable- ymlish - also seed the current state into the log below v --- ccng: image: cloudfoundry/cloud-controller-ng@sha256:7b2856677f079539f9fb7c1179df0e763077d9e6b18dca8394400c3e1bc879bf sha: c743feaae5fc3081a76c9a7ba8bd550f06ae2686 remote: https://github.com/cloudfoundry/cloud_controller_ng nginx: image: cloudfoundry/capi-nginx@sha256:980f50e190cbff72d23300bc422da23faa888271c2d07ac3abaa65af55a5316a sha: 56c57636971a434658a0dc4e1225648b3bb26d85 remote: https://github.com/cloudfoundry/capi-k8s-release.git cf_api_controllers: image: cloudfoundry/cf-api-controllers@sha256:9cd6557f411c42b2bafe8487f63fae608f0dafd9f56c4268de8ec6fcd88ff7d9 sha: 56c57636971a434658a0dc4e1225648b3bb26d85 remote: https://github.com/cloudfoundry/capi-k8s-release.git package_image_uploader: image: cloudfoundry/cf-api-package-image-uploader@sha256:aae727a0960d10ce644035dee7041f7e882c7c58a37992252002ce7c95d8804d sha: 56c57636971a434658a0dc4e1225648b3bb26d85 remote: https://github.com/cloudfoundry/capi-k8s-release.git Authored-by: Connor Braa <[email protected]>
push time in 8 days
PR opened cloudfoundry/cf-for-k8s
Resubmitted to appease CI.
this allows us to remove cert configuration and bogus defaults from capi-k8s-release default values files.
WHAT is this change about?
This removes a few unnecessary properties from capi.yml that used to configure TLS communication between CAPI and eirini.
Does this PR introduce a change to config/values.yml?
No.
Acceptance Steps
It should deploy without a hitch. After this is merged, please poke us to merge cloudfoundry/capi-k8s-release#68 .
pr created time in 8 days
create barnchcloudfoundry/capi-bara-tests
branch : wip-more-k8s-baras-174425881
created branch time in 9 days
issue commentcloudfoundry/cf-k8s-networking
Generalize Route CRD to be less Cloud Foundry-specific
Route CR is a part of Cloud Foundry
remove "cf"
a desire to expunge "Cloud Foundry"
I hope I'm not derailing, but I think I'm detecting an opportunity for better nomenclature here. In this thread people are using "CF" to refer both to our broad organization (the thing the Route CR is a part of) AND the CF API (the thing that the Route CR ought nought to be specific to, sometimes in the same sentence. If we draw the distinction between these 2 things, I think maybe we'd have an easier time communicating.
Out of curiosity, does the Cloud Controller (CAPI) team have any plans to remove "cf-[API]" from their components (e.g cf-api-server, cf-api-worker, etc)?
identify extension points that don't have to be Cloud Foundry [API]-specific
coupled to [the] CF [API] out of necessity.
I think the analogous thing here is that there's a tiny bit of code starting to form in cf-api-controllers that we might decouple from the API. Most of that component is coupled tightly to the CF API, like Tim says, but there's a TINY bit of glue that watches for kpack stack updates and applies their resulting image changes to Eirini's StatefulSets - an operation that could be useful 100% independent of the involvement of the CF API.
One day we may want to extract that thing to be part of an cf-app-controllers that we might deploy without a CF API or the rest of cf-api-controllers.
Tim's suggested changes to Route echo this intent: in the Route CRD, what could we decouple from the specifics of the CF API?
comment created time in 11 days
PR opened cloudfoundry/capi-k8s-release
these are not necessary.
requires https://github.com/cloudfoundry/cf-for-k8s/pull/425
pr created time in 11 days
create barnchcloudfoundry/capi-k8s-release
branch : remove-eirini-cert-defaults
created branch time in 11 days
PR opened cloudfoundry/cf-for-k8s
this allows us to remove cert configuration and bogus defaults from capi-k8s-release default values files.
WHAT is this change about?
This removes a few unnecessary properties from capi.yml that used to configure TLS communication between CAPI and eirini.
Does this PR introduce a change to config/values.yml?
No.
Acceptance Steps
It should deploy without a hitch. After this is merged, please poke us to merge TBD
pr created time in 11 days
create barnchcloudfoundry/cf-for-k8s
branch : remove-capi-eirini-internal-certs
created branch time in 11 days
issue commentcloudfoundry/cloud_controller_ng
is it possible that
processes:
- type: web
command: /layers/paketo-buildpacks_go-mod/app-binary/bin/main
causes the issue? are custom commands working today in the CNB push flow?
comment created time in 11 days
issue commentcloudfoundry/capi-k8s-release
Scale out of cf-api-server doesn't work beyond 5 replicas in cf-for-k8s
Hi @KesavanKing! Could you look for the associated log line in the cf-api-server logs? It should have a backtrace that we could use to narrow down what the issue is here.
comment created time in 11 days
push eventcloudfoundry/capi-k8s-release
commit sha 402249eadf278bab755db3461fa2669731623fca
hardcode `skip_cert_verify: false` on capi-k8s-release - secure-by-default and most things are service-meshed anyways [finishes #173974998] Authored-by: Connor Braa <[email protected]>
push time in 11 days
issue closedcloudfoundry/capi-k8s-release
see Credhub and cf-for-k8s Password Generation
We need to make an effort to get capi-k8s-releases' secrets out of its big global configmap. Part of doing this will be removing unnecessary TLS certificates out of capi-k8s-release, but there are more secrets hiding in the configmap:
- https://github.com/cloudfoundry/cf-for-k8s/issues/228 CAPI UAA client secret is stored as a plain text in value in cloud-controller-ng-yaml configmap
- https://github.com/cloudfoundry/cf-for-k8s/issues/227 The CC blobstore access key is stored as a plain text value to cloud-controller-ng-yaml configmap
- https://github.com/cloudfoundry/cf-for-k8s/issues/226 The CC database password is passed as a plain text value to cloud-controller-ng-yaml config
- https://github.com/cloudfoundry/cf-for-k8s/issues/225 UAA client password is passed as a plain text to
cf-api-kpack-watcher
I think we'd also need to handle the database encryption keys.
closed time in 11 days
cwlbraa
issue commentcloudfoundry/capi-k8s-release
done in 3 stories:
eirini certs: https://www.pivotaltracker.com/story/show/173905990 capi: https://www.pivotaltracker.com/story/show/173973874 cf-api-controllers: https://www.pivotaltracker.com/story/show/173973896
comment created time in 11 days
issue commentcloudfoundry/capi-k8s-release
CAPI api server runs out of DB connections
We'd really like to be able to increase the max connections on that postgres. Alternatively we could tune down the size of the connection pools.
comment created time in 11 days
issue commentcloudfoundry/capi-k8s-release
CAPI performance issues at scale
This probably needs to be revisited.
- We ultimately decided not to support capi-k8s-release+cf6.
- [VAT did some work to make v3/apps faster shortly after this issue was created and discussed.
- It's possible this is still slow due to eirini instance reporter performance.
comment created time in 11 days
push eventcwlbraa/.dotfiles
commit sha d2cf9e0db12982b9775ffdf17ee244340e7f7d93
switch to brave - also add python to layers
push time in 14 days
push eventcloudfoundry/capi-dockerfiles
commit sha f09db012ed4ad257eb682c4e1a00e8f009e45b70
install gnupg so we can add the cf repo to package lists Co-authored-by: Connor Braa <[email protected]> Co-authored-by: Piyali Banerjee <[email protected]>
push time in 17 days
push eventcloudfoundry/capi-dockerfiles
commit sha 97ffa4b6758f7f80423ff216241ef7bf29ded7ca
install cf7 as cf in cf-for-k8s ci dockerfile Co-authored-by: Connor Braa <[email protected]> Co-authored-by: Piyali Banerjee <[email protected]>
push time in 17 days
push eventcloudfoundry/capi-ci
commit sha fa52f261fc5e98d08fd014382b4b52014c1753ac
remove -race because we don't have cgo Co-authored-by: Connor Braa <[email protected]> Co-authored-by: Piyali Banerjee <[email protected]>
push time in 17 days
push eventcloudfoundry/capi-ci
commit sha 06c69d53014b4b1c87d25a124910b6a60b8275d3
copy samus directory, not its contents Co-authored-by: Connor Braa <[email protected]> Co-authored-by: Piyali Banerjee <[email protected]>
push time in 17 days
push eventcloudfoundry/capi-ci
commit sha ccea7f732f8b58453a542845b671f21fcfdf4df0
try to be more consistent about copying and writing env-metadata in deploy-cf-for-k8s Co-authored-by: Connor Braa <[email protected]> Co-authored-by: Piyali Banerjee <[email protected]>
push time in 17 days
push eventcloudfoundry/capi-ci
commit sha 99f7a0705d6b257285c5b3fae0c80f8a10ebaac2
temporarily allow samus to redeploy without deleting/regening vars Co-authored-by: Connor Braa <[email protected]> Co-authored-by: Piyali Banerjee <[email protected]>
push time in 17 days
Pull request review commentcloudfoundry/cloud_controller_ng
Name | Type | Description **type** | _string_ | `docker` **data** | _object_ | Data is not used by the Docker lifecycle; valid value is `{}` +### Kpack lifecycle++```+Example Kpack Lifecycle+```++```json+{+ "type": "kpack",+ "data": {+ "buildpacks": ["paketo-buildpacks/java"]+ }+}+```++This is the default lifecycle for Cloud Foundry for Kubernetes. When staging an app with this lifecycle, the app source code will be+compiled using a [Cloud Native Buildpack](https://buildpacks.io/) by [kpack](https://github.com/pivotal/kpack), resulting in an OCI image. When running an app with this lifecycle,+a container is created and the OCI image is executed inside of it.
might worth mentioning that the build creates a docker lifecycle droplet
comment created time in 17 days
push eventcloudfoundry/cloud_controller_ng
commit sha 534a7427c10bb08a26c17d3894d3ae9016aba194
update image source on build - including in-place upgrade from package-blobstore to package-registry [#173343000] Co-authored-by: Connor Braa <[email protected]> Co-authored-by: Piyali Banerjee <[email protected]>
push time in 19 days
push eventcloudfoundry/capi-ci
commit sha 80255a5bd13511511ad3c672e3800dadbe7c1405
wire package-image-uploader into bump-capi-k8s-release-image-refs [#173343000] Co-authored-by: Connor Braa <[email protected]> Co-authored-by: Piyali Banerjee <[email protected]>
push time in 19 days
push eventcloudfoundry/capi-k8s-release
commit sha 8a6f7cbe8481ee26405f9c719000b14eea212e41
deploy package-image-uploader and wire it into local-worker - includes some kbld fixes for local builds - make package-image-uploader run as root to access nginx-written zipfiles. we might want to do some smart `chown`ing later - create and mount secret for registry uploads [finishes #173343000] Co-authored-by: Connor Braa <[email protected]> Co-authored-by: Piyali Banerjee <[email protected]>
push time in 19 days
push eventcloudfoundry/capi-ci
commit sha 47c7fea04e76da8a1a04051d103c3517839c8685
start wiring package-image-uploader into samus Co-authored-by: Connor Braa <[email protected]> Co-authored-by: Piyali Banerjee <[email protected]>
push time in 19 days
push eventcloudfoundry/capi-ci
commit sha 10c1d20f3e5b1354c5642a9a2db232de3caeedf2
go get AND go install ginkgo Co-authored-by: Connor Braa <[email protected]> Co-authored-by: Piyali Banerjee <[email protected]>
push time in 19 days
push eventcloudfoundry/capi-ci
commit sha 5654ba0c6415e8800d8a7ebbddac245a39d2420c
install ginkgo when running package-image-uploader tests Co-authored-by: Connor Braa <[email protected]> Co-authored-by: Piyali Banerjee <[email protected]>
push time in 19 days
issue commentcloudfoundry/cf-for-k8s
Replace minio blobstore with an OCI compliant registry
for clarity, in the CF API "source code" is usually referred to as "packages," and in the capi backlog we talk about this as a "package registry"
comment created time in 19 days
push eventcloudfoundry/capi-ci
commit sha 701b3220a694f27dc4ebe62d2706f4fbce75cf28
fixup: bad copying Co-authored-by: Connor Braa <[email protected]> Co-authored-by: Piyali Banerjee <[email protected]>
push time in 19 days
push eventcloudfoundry/capi-ci
commit sha 707c1662f75716d8b9a03a36555b8b4fd76c7c79
build package-image-uploader in ci [#173343000] Co-authored-by: Connor Braa <[email protected]> Co-authored-by: Piyali Banerjee <[email protected]>
push time in 19 days
issue closedcloudfoundry/cloud_controller_ng
API to get app memory utilisation at a given point of time
Thanks for submitting an issue to cloud_controller_ng. We are always trying to improve! To help us, please fill out the following template.
API to get app memory utilisation at a given point of time
All i need is to know if there is an API in cloud foundary which gives the memory metrics of the application at a particular time like whats its memory, cpu uitlisation?
closed time in 19 days
bhanuReddy2695
issue commentcloudfoundry/cloud_controller_ng
API to get app memory utilisation at a given point of time
http://v3-apidocs.cloudfoundry.org/version/3.83.0/index.html#get-stats-for-a-process
comment created time in 19 days
push eventcloudfoundry/cloud_controller_ng
commit sha cfd226233cf9d33b1b971ba6b7e8c0577a89425a
build(deps): bump kubeclient from 4.9.0 to 4.9.1 (#1816) Bumps [kubeclient](https://github.com/abonas/kubeclient) from 4.9.0 to 4.9.1. - [Release notes](https://github.com/abonas/kubeclient/releases) - [Changelog](https://github.com/abonas/kubeclient/blob/master/CHANGELOG.md) - [Commits](https://github.com/abonas/kubeclient/compare/v4.9.0...v4.9.1) Signed-off-by: dependabot[bot] <[email protected]> [finishes #174574231] Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
push time in 19 days
PR merged cloudfoundry/cloud_controller_ng
Bumps kubeclient from 4.9.0 to 4.9.1. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/abonas/kubeclient/blob/master/CHANGELOG.md">kubeclient's changelog</a>.</em></p> <blockquote> <h2>4.9.1 — 2020-08-31</h2> <h3>Fixed</h3> <ul> <li>Now should work with apiserver deployed not at root of domain but a sub-path, which is standard with Rancher. Notably, <code>create_...</code> methods were sending bad apiVersion and getting 400 error. (<a href="https://github-redirect.dependabot.com/abonas/kubeclient/issues/457">#457</a>, hopefully fixes <a href="https://github-redirect.dependabot.com/abonas/kubeclient/issues/318">#318</a>, <a href="https://github-redirect.dependabot.com/abonas/kubeclient/issues/418">#418</a> and <a href="https://gitlab.com/gitlab-org/gitlab/-/issues/22043">https://gitlab.com/gitlab-org/gitlab/-/issues/22043</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/abonas/kubeclient/commit/cb20e10a988e9643a25ce397cbc84c772cdf3558"><code>cb20e10</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/abonas/kubeclient/issues/458">#458</a> from cben/release-4.9.1</li> <li><a href="https://github.com/abonas/kubeclient/commit/229e3c0724d177943550aeb5b344daab1443f7fa"><code>229e3c0</code></a> Bump kubeclient to 4.9.1</li> <li><a href="https://github.com/abonas/kubeclient/commit/520a6568c6ff517ba299337b0ec4ceac75b6c42f"><code>520a656</code></a> changelog for <a href="https://github-redirect.dependabot.com/abonas/kubeclient/issues/457">#457</a>, releasing as 4.9.1</li> <li><a href="https://github.com/abonas/kubeclient/commit/2542ff80ad0e2ddee58d6bd93497261d57bf64be"><code>2542ff8</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/abonas/kubeclient/issues/457">#457</a> from T4cC0re/nested_api</li> <li>See full diff in <a href="https://github.com/abonas/kubeclient/compare/v4.9.0...v4.9.1">compare view</a></li> </ul> </details> <br />
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
<details> <summary>Dependabot commands and options</summary> <br />
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
</details>
pr closed time in 19 days
push eventcloudfoundry/capi-workspace
commit sha ad6ea65b214a74d0bab0c14d18abde668ec726d8
use new versioned cf cli taps Authored-by: Connor Braa <[email protected]>
push time in 22 days
pull request commentcloudfoundry/capi-k8s-release
Set memory and cpu requests and limit values for all containers
thanks for this! the only change I'd make to what's here is:
- worker, deployment_updater, and clock should all be allowed 1000m CPU, and request 300m. They're GIL'd and sometimes do compute-intensive tasks, but are mostly idle.
are y'all interested in adding the configurability to this PR? maybe to build some empathy for how cf-for-k8s component teams add optional config parameters to cf-for-k8s?
Things that should be configurable:
- cf-api-server instance count
- worker instance count
- clock memory limit (and request?)
- deployment updater memory limit (and request?)
- cf-api-controllers memory limit (and request?) AND CPU limit/request
comment created time in 22 days
Pull request review commentcloudfoundry/capi-k8s-release
Set memory and cpu requests and limit values for all containers
spec: imagePullPolicy: Always resources: requests:+ cpu: 500m memory: 300Mi limits:+ cpu: 1000m memory: 1.2Gi
It was probably a raw multiple of the initially-deployed memory usage. We set these to keep the API from getting OOM killed, not based on any experiment to produce memory bloat or "realistic" workloads.
comment created time in 22 days
push eventcloudfoundry/capi-k8s-release
commit sha 2ed7ae930f37199ff1ff2524e035f75e3d996be5
use public cf-api-package-image-uploader image by default [#173343000] Authored-by: Connor Braa <[email protected]>
commit sha 63ece3a33c3da34a8fd39ac82b0e738365b670da
wip: deploy package-image-uploader Authored-by: Connor Braa <[email protected]>
push time in 22 days
push eventcloudfoundry/capi-k8s-release
commit sha 2ed7ae930f37199ff1ff2524e035f75e3d996be5
use public cf-api-package-image-uploader image by default [#173343000] Authored-by: Connor Braa <[email protected]>
push time in 22 days
push eventcloudfoundry/capi-ci
commit sha 2bd85fb4c3ffda79133bbba613ce917f3e0524aa
try running more baras simultaneously on samus [#173343000] Authored-by: Connor Braa <[email protected]>
push time in 22 days
push eventcloudfoundry/capi-ci
commit sha f1d469a6de8f134650865b53a96be868f112fce6
finish rename of cf-api-controllers [#173343000] Authored-by: Connor Braa <[email protected]>
push time in 22 days
create barnchcloudfoundry/capi-k8s-release
branch : package-registry-#173343000
created branch time in 22 days
push eventcloudfoundry/capi-k8s-release
commit sha 0655143662cffd0d16444405b7a4d0bfe523cb50
make package-image-uploader kbld/pack buildable [#173343000] Authored-by: Connor Braa <[email protected]>
push time in 22 days
push eventcloudfoundry/cloud_controller_ng
commit sha e40fdb3d39878dca72aa3ebee50eef64082dd906
enable package registry uploads when configured - upload packages to registry when package_image_uploader is configured - make stager tell kpack to download registry packages when packages.image_registry is configured [#173343000] Co-authored-by: Connor Braa <[email protected]> Co-authored-by: Piyali Banerjee <[email protected]>
push time in 24 days
push eventcwlbraa/.dotfiles
commit sha dbf232c0341521702868bdaef5d619e407619124
fix vterm ctrl-r
commit sha 31738f8e9a579cf73b0c988dde30f058ec3336d9
disable conky
push time in a month
push eventcwlbraa/.dotfiles
commit sha 9d83ff79b5529910a892a70557dc863f2013dc1a
i3 polishing - switch lock to always use lightdm instead of i3lock bs - add icons to status bar - move dotfiles to their own directory - make rofi cuter - customize i3 gruvbox theme a bit 4 cuter floating windows - clean up other crufty nonsense & dead code
push time in a month
push eventcwlbraa/.dotfiles
commit sha 4d5f9607e5d05f2f767f6af78f9fa197bc445751
gruvboxify i3 config
commit sha 4c9f7d81b147f711d3ed8a9ec7897d85d8385bbf
fix emacsclient command for i3 window 1
commit sha c5a5c1aca9a11306b5cfd20509eb4ed1f1c27786
tune a bunch of spacemacs options and reorg layers
push time in a month
create barnchcloudfoundry/capi-k8s-release
created branch time in a month
push eventcloudfoundry/capi-k8s-release
commit sha 3340510e1d78592862ff80cb9eb0dc9787bce217
Remove TLS for metric-proxy (#63) * Revert "Merge pull request #53 from cloudfoundry/revert-51-remove-tls-metric-proxy" This reverts commit 4b606d7e560af69c529f8cae42d5446e8a2a8566, reversing changes made to 0ca02ba39e5c6e1d73892ff2bf34e7ba8cf8af10. Co-authored-by: Lou "THE MAN" Brann <[email protected]> * add certs back to _default.yml [#173597144] [finishes #174307225] Co-authored-by: Lou "THE MAN" Brann <[email protected]>
push time in a month
PR merged cloudfoundry/capi-k8s-release
This reverts commit 4b606d7e560af69c529f8cae42d5446e8a2a8566, reversing changes made to 0ca02ba39e5c6e1d73892ff2bf34e7ba8cf8af10.
pr closed time in a month
issue closedcloudfoundry/capi-k8s-release
CF push of spring-music app with v7 CLI fails after building app image
Original issue on cf-for-k8s: https://github.com/cloudfoundry/cf-for-k8s/issues/287
Based on associated slack threads (https://cloudfoundry.slack.com/archives/CH9LF6V1P/p1594916021423300 and https://cloudfoundry.slack.com/archives/CH9LF6V1P/p1594928317432200), CC's behavior in cf-for-k8s seems to be the cause, so I'm opening an issue on the capi-k8s-release repo for the CAPI team to track.
closed time in a month
emalm
issue commentcloudfoundry/capi-k8s-release
CF push of spring-music app with v7 CLI fails after building app image
should be fixed in eirini now: https://github.com/cloudfoundry-incubator/eirini/issues/104
comment created time in a month
push eventcloudfoundry/capi-k8s-release
commit sha 0c7a73be643d89aad37c2fe892d8ef82c12ce45c
Allow aws_signature_version to be configured Co-authored-by: Benjamin Haegenlaeuer <[email protected]>
commit sha e3a83f5c7ea3e83cbc71d46909317ee71cd85012
Merge pull request #64 from sap-contributions/configure-aws-signature-version makes AWS signature version configurable [finishes #174377076]
push time in a month
PR merged cloudfoundry/capi-k8s-release
This is the first step in a series to support external blobstores and allows the aws_signature_version setting to be configured.
See #344 for more details.
@Haegi
pr closed time in a month
push eventcloudfoundry/capi-k8s-release
commit sha 866214347ab8d7434a3dbc6cb19d6b1828d2340c
have envoy skip metrics port on cf-api-server - lack of hostname when prom is scraping messes up connectivity [#174150895] Co-authored-by: Connor Braa <[email protected]> Co-authored-by: Tim Downey <[email protected]>
push time in a month
push eventcloudfoundry/capi-k8s-release
commit sha e7a3d40d09f00cef8a1fa79f82a9037d73cf0a9d
scripts/console.sh update so it works w/ new secrets locations Authored-by: Connor Braa <[email protected]>
push time in a month
push eventcloudfoundry/cloud_controller_ng
commit sha 861bda8332092b0c10493764001ee92108d71f3e
make console load config from files specified by env vars Co-authored-by: Connor Braa <[email protected]> Co-authored-by: Tim Downey <[email protected]>
push time in a month
push eventcwlbraa/.dotfiles
commit sha 4c5e7ca36acbc9769073b684fd1bba86d5265f02
fix spacemacs mouse weirdness
push time in a month
push eventcloudfoundry/cloud_controller_ng
commit sha 028c9c1269808e021803a3f817870b64879dac02
build(deps-dev): bump solargraph from 0.39.13 to 0.39.14 (#1784) Bumps [solargraph](https://github.com/castwide/solargraph) from 0.39.13 to 0.39.14. - [Release notes](https://github.com/castwide/solargraph/releases) - [Commits](https://github.com/castwide/solargraph/compare/v0.39.13...v0.39.14) Signed-off-by: dependabot[bot] <[email protected]> [finishes #174316051] Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
push time in a month