community icon indicating copy to clipboard operation
community copied to clipboard

Request: create a coredns icon

Open spurin opened this issue 2 years ago • 5 comments
trafficstars

Describe the issue

In the icons set, there does not appear to be an icon for coredns. I was able to modify one of the icons to accomplish this but for reasons I don't know, the alignment doesn't work as expected when scaling the .svg file to a png via the rasterize.sh script. Exporting direct from illustrator however, had the desired result and in the interim, I'm using this version. For completeness it would be great if this existed with it being a core component (rather than it being treated as just a deployment).

Possibly, there is an alignment step in the source svg creation that I am missing. If the creator of these icons can include this icon it would be greatly appreciated.

For reference, this is the set of current icons.

% find . -type f -name "*.svg" -exec basename {} \; | sort -u
api.svg
c-c-m.svg
c-m.svg
c-role.svg
cm.svg
control-plane.svg
crb.svg
crd.svg
cronjob.svg
deploy.svg
ds.svg
ep.svg
etcd.svg
group.svg
hpa.svg
ing.svg
job.svg
k-proxy.svg
kubelet.svg
limits.svg
netpol.svg
node.svg
ns.svg
pod.svg
psp.svg
pv.svg
pvc.svg
quota.svg
rb.svg
role.svg
rs.svg
sa.svg
sc.svg
sched.svg
secret.svg
sts.svg
svc.svg
user.svg
vol.svg

Many Thanks

James Spurin

spurin avatar May 26 '23 09:05 spurin

/sig docs

spurin avatar May 26 '23 09:05 spurin

Hey @spurin , if you are referring to the icons under kubernetes/community, SIG Docs is not responsible for maintaining and/or creating the icons. As the co-chair, I'm untagging our SIG & request that you bring it up in one of the contributor experience meetings. /remove-sig docs

divya-mohan0209 avatar Aug 16 '23 06:08 divya-mohan0209

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Jan 26 '24 12:01 k8s-triage-robot

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot avatar Feb 25 '24 13:02 k8s-triage-robot

/sig network

pranav-pandey0804 avatar Mar 10 '24 09:03 pranav-pandey0804

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Reopen this issue with /reopen
  • Mark this issue as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-triage-robot avatar Apr 09 '24 10:04 k8s-triage-robot

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Reopen this issue with /reopen
  • Mark this issue as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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.

k8s-ci-robot avatar Apr 09 '24 10:04 k8s-ci-robot