Origin: Use a FontAwesome (or custom) icon for template

Created on 14 Oct 2018 · 7Comments · Source: openshift/origin

I want to use a FontAwesome or a custom icon for my template.

There is iconClass attribute in template.metadata.annotation mentioned in dev_guide:

An icon to be displayed with your template in the web console. Choose from our existing logo icons when possible. You can also use icons from FontAwesome and PatternFly. Alternatively, provide icons through CSS customizations that can be added to an OpenShift Container Platform cluster that uses your template. You must specify an icon class that exists, or it will prevent falling back to the generic icon

when I set the iconClass to default openshift logos like icon-laravel it works and I can see the icon in template catalog but I don't know how to use a FontAwesome logo. I tried using ghost, fa fa-ghost and fas fa-ghost as mentioned FontAwesome basic use but none of them worked.
how can I use non-default logos such as FontAwesome for an openshift template ?

Version

openshift v3.10.0+91d44f1-52
kubernetes v1.10.0+b81c8f8

Steps To Reproduce

create a template with this starting.

apiVersion: v1
kind: Template
metadata:
  name: test
  annotations:
    iconClass: "ghost"

Current Result

No image is shown as Icon.

Expected Result

The FontAwesome ghost icon.

lifecyclrotten

Source

amirmasud

Most helpful comment

I've asked it on stack overflow days ago too. Fortunately, someone answered.
Currently version 4.7 of Font Awesome icons is supported on openshift web console. We may create an issue there to support version 5.

amirmasud on 21 Oct 2018

👍2

All 7 comments

I'm also asking the same question. Unfortunately the documentation is not clear about that point.
Any explanation please ?

abessifi on 21 Oct 2018

amirmasud on 21 Oct 2018

👍2

Personally what I'm looking for is how to include a custom icons (not from default staff) for OKD 3.7 for instance. In the documentation we talk about custom CSS configuration to include such icons but it's not clear how to do that.

abessifi on 21 Oct 2018

👍1

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

openshift-bot on 19 Jan 2019

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

openshift-bot on 19 Feb 2019

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

openshift-bot on 21 Mar 2019

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/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.