profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/ahmetb/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Ahmet Alp Balkan ahmetb Google Seattle, WA https://ahmet.dev Software Engineer at Google Cloud on cloud-native technologies and serverless platforms: Kubernetes/GKE and Cloud Run.

ahmetb/cloud-run-faq 1725

Unofficial FAQ and everything you've been wondering about Google Cloud Run.

ahmetb/azurefs 71

Mount Microsoft Azure Blob Storage as local filesystem in Linux (inactive)

ahmetb/cloud-run-multi-region-terraform 49

Deploy a Cloud Run app to all available regions using Terraform.

ahmetb/cloud-run-iap-terraform-demo 17

Deploy an IAP-secured application to Cloud Run using Terraform (e.g. an admin portal or internal company app)

ahmetb/cloud-run-button 5

Allow your GitHub repos to deploy to Google Cloud Run in a single click

ahmetb/blobmetadb 3

Watches your application’s Microsoft Azure Blob Storage requests and keeps record of your blobs on Redis.

ahmetb/cloud-run-hello 3

Sample Cloud Run application

ahmetb/awesome-grpc 2

A curated list of useful resources for gRPC

startedahmetb/kubernetes-network-policy-recipes

started time in an hour

issue commentkubernetes-sigs/krew

Proposal: implement a manifest style validation tool for krew-index specifically

@fejta-bot: Closing this issue.

<details>

In response to this:

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community. /close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. </details>

ahmetb

comment created time in 2 hours

issue closedkubernetes-sigs/krew

Proposal: implement a manifest style validation tool for krew-index specifically

Currently, our plugin manifest validation functionality which is in the YAML parsing path has some style/cosmetic checks that have no effect on plugin installation. This is a result of not separating "cosmetic validation" and "functional validation".

If we continue on this trajectory, we will be adding more "cosmetic validation" in future versions, which will break older plugin manifests. So we can't do that. Furthermore, with custom plugin indexes (#566), we cannot control the plugin manifests out in the wild –but we have to be able to continue working with them.

I propose that we strip off these "cosmetic validations" from the logic in krew machinery, and create a krew_index_manifest_validator tool, specifically for krew-index that runs as part of its CI for each PR.

This would help reduce code review toil we have been manually enforcing in krew-index, as well as separate structural validation vs cosmetic validation, such as:

  • shortDescription must not contain line break characters
  • shortDescription must not have a a trailing period (.)
  • description must be wrapped at 80 character lines
  • explicit files: {from: '*', to: '.'} is not needed, drop
  • after executing files on specified archive, there should be a LICENSE file in the directory.
  • [... other stuff that I can't think about right now...]

The problem is: We already have some validation in cmd/validate-krew-manifest tool that is run only for krew-index. This validation:

  1. runs all structural validation through Validate()
  2. ensures: all spec.platforms[] items are used
  3. ensures: no overlapping spec.platform[].selectors
  4. ensures: all spec.platforms[] install fine
  • point 1: Already validated by krew, during parsing
  • point 2: Not a functional validation, if there's unused platforms[], krew continues to work fine.
  • point 3: I believe Krew continues to work fine when there are overlapping selectors –though, the behavior is undefined (not sure which one would be picked up, as we don't guarantee it). We could move this to "functional validation", though I'm not sure we totally should.
  • point 4: Not "structural validation", just ensures plugins merged to krew-index are installable, we can't enforce this in custom indexes.

So maybe we just make cmd/validate-krew-manifest more about "styling" and make it clear it's meant for krew-index.


/kind proposal /cc @corneliusweig

closed time in 2 hours

ahmetb

issue commentkubernetes-sigs/krew

Proposal: implement a manifest style validation tool for krew-index specifically

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community. /close

ahmetb

comment created time in 2 hours

startedahmetb/cloud-run-faq

started time in 4 hours

push eventahmetb/twitter-audit-log

github-actions[bot]

commit sha c83c19c9f4212de98605c980d9fa41db987d55f9

Periodic update: 2021-06-23 21:52:23+00:00

view details

push time in 5 hours

startedahmetb/runsd

started time in 6 hours

startedahmetb/kubectx

started time in 6 hours

push eventkubernetes-sigs/krew-index

krew-release-bot

commit sha b5e347a9db6aa5bd736b028a85fe353a14e2099c

new version v0.19.0 of reliably (#1350)

view details

push time in 12 hours

PR merged kubernetes-sigs/krew-index

Reviewers
release new version v0.19.0 of reliably approved cncf-cla: yes lgtm size/S

hey krew-index team,

I am krew-release-bot, and I would like to open this PR to publish version v0.19.0 of reliably on behalf of @reliably-ci.

Thanks, @krew-release-bot

+5 -5

2 comments

1 changed file

krew-release-bot

pr closed time in 12 hours

pull request commentkubernetes-sigs/krew-index

release new version v0.19.0 of reliably

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: <a href="https://github.com/kubernetes-sigs/krew-index/pull/1350#issuecomment-866909701" title="Approved">ahmetb</a>, <a href="https://github.com/kubernetes-sigs/krew-index/pull/1350#" title="Author self-approved">krew-release-bot</a>

The full list of commands accepted by this bot can be found here.

The pull request process is described here

<details > Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment </details> <!-- META={"approvers":[]} -->

krew-release-bot

comment created time in 12 hours

PR opened kubernetes-sigs/krew-index

release new version v0.19.0 of reliably

hey krew-index team,

I am krew-release-bot, and I would like to open this PR to publish version v0.19.0 of reliably on behalf of @reliably-ci.

Thanks, @krew-release-bot

+5 -5

0 comment

1 changed file

pr created time in 12 hours

startedahmetb/kubectx

started time in 12 hours

release grafana/grafana

v7.5.9

released time in 12 hours

fork SambariSrinivas/kubernetes-network-policy-recipes

Example recipes for Kubernetes Network Policies that you can just copy paste

fork in 16 hours

startedahmetb/kubectx

started time in 16 hours

startedahmetb/kubernetes-network-policy-recipes

started time in 17 hours

startedahmetb/kubernetes-network-policy-recipes

started time in 17 hours

startedahmetb/kubernetes-network-policy-recipes

started time in 17 hours

startedahmetb/kubernetes-network-policy-recipes

started time in 17 hours

issue openedahmetb/cloud-run-faq

Will Cloud Run release some memory when instances being idle?

I'm curious that why memory are kept when Idle

created time in 18 hours

release alicebob/miniredis

v2.15.0

released time in 19 hours

startedahmetb/kubectx

started time in 19 hours

fork bmbbms/kubernetes-network-policy-recipes

Example recipes for Kubernetes Network Policies that you can just copy paste

fork in 20 hours

startedahmetb/go-linq

started time in 21 hours

startedahmetb/kubectx

started time in a day

fork yemisi/kubernetes-network-policy-recipes

Example recipes for Kubernetes Network Policies that you can just copy paste

fork in a day

PR opened ahmetb/cloud-run-faq

Update default value for concurrency

Thank you for this awesome resource. I believe the default value for concurrency is out of date - the referenced doc state "By default each Cloud Run container instance can receive up to 80 requests at the same time..."

Thanks!

+1 -1

0 comment

1 changed file

pr created time in a day

fork nickmeinhold/cloud-run-faq

Unofficial FAQ and everything you've been wondering about Google Cloud Run.

https://cloud.run

fork in a day

startedahmetb/cloud-run-faq

started time in a day