Table of Contents
Custom Styling options for a portal
|cssStylesheet||common.portal.gloo.solo.io.DataSource||Custom CSS stylesheet that will be applied to the portal. Custom stylesheets take precedence over the other styling attributes in this object.|
|name||string||The name of the page.|
|description||string||Description of the page.|
|path||string||The path for this page relative to the portal base URL.|
|navigationLinkName||string||The name of the link displayed on the portal navigation bar.|
|displayOnHomepage||bool||Set to true if you want to display a tile that links to the static page on the portal home page. Only one of the static pages for a portal can set this flag to true.|
|content||common.portal.gloo.solo.io.DataSource||Content for the page, markdown in the case of Static pages, url inline_string in the case of Dynamic|
A Portal tells the Gloo Portal operator to fetch and serve static assets which are used by the Gloo Portal UI. Each portal can publish one or more APIProducts.
|displayName||string||Display name of the portal.|
|description||string||Description for the portal.|
|domains||string||repeated||The domains on which this Portal will be served. The Host header received by the Portal Web App will be matched to one of these domains in order to determine which Portal will be served.
If you are using Gloo Edge and the Gateway through which you are exposing the Portal is listening on a port other than 80⁄443, you should include the port as part of the domain string, e.g. “portal.solo.io:8443”.
To prevent undefined behavior, creating a Portal whose domain conflicts with an existing Portal or Environment will result in the Portal resource being placed into an ‘Invalid’ state.
|primaryLogo||common.portal.gloo.solo.io.DataSource||Logo to display on the portal.|
|favicon||common.portal.gloo.solo.io.DataSource||Browser favicon for the portal.|
|banner||common.portal.gloo.solo.io.DataSource||The banner image for the portal.|
|customStyling||CustomStyling||Custom Styling overrides.|
|staticPages||PageSpec||repeated||Static markdown content pages for the Portal.|
|dynamicPages||PageSpec||repeated||Dynamic pages that should be included in the Portal.|
|enableIngress||google.protobuf.BoolValue||Generate an ingress route from this Portal’s domains to the web application serving this portal. Defaults to true.|
|oidcAuth||PortalSpec.OidcAuth||Set this field to allow users to authenticate with the Portal using an OIDC Identity Provider.|
|tls||gloo.solo.io.SslConfig||This field is required to correctly configure TLS on the
|publishedEnvironments||PortalSpec.EnvironmentSelector||repeated||Determines which Environments and APIProducts will be published in the Portal.
The set of Environments and APIProducts a specific user sees upon login will be filtered by the permissions associated either with that User, or with the Groups that the user is a member of.
If the Environments/APIProducts published in the Portal do not intersect with the ones accessible by the User, the user will see no APIProducts.
|allApisPublicViewable||bool||Controls the behavior of the Portal for users who are not logged in. By default, the Portal requires login to see API Products. If true, all APIs are visible to all users (even those who aren’t logged in).|
|portalUrlPrefix||string||The prefix URL must match the URL used by users to reach the portal. This should be in the format <http|
|name||string||The name of the Environment to publish.|
|namespace||string||The namespace of the Environment to publish.|
|apiProducts||common.portal.gloo.solo.io.ObjectRef||repeated||Use this field to only publish a subset of the APIProducts included in the Environment. If empty, all APIProducts included in the Environment will be published in the Portal.|
Configuration parameters for authenticating to a Portal using OIDC. Acts as an alternative to Gloo Portal’s built-in User management
|issuer||string||The issuer is the URL identifier for the service. For example: “https://accounts.google.com"|
|clientId||string||The Client ID used to register with the OIDC provider.|
|clientSecret||common.portal.gloo.solo.io.SecretRef||Reference to a Kubernetes secret containing the OIDC Client Secret to be used to register with the OIDC authentication server. The default key used to look up the secret will be
|groupClaimKey||string||The Key of the OIDC claim containing the names of the Groups which are authorized to access this portal. The OIDC Server must return a space-separated list of Group names, which contain one the oidc_group_name of one or more OIDC Groups.|
|additionalScopes||string||repeated||Any additional scopes to be included in the request. By default, “openid”, “profile”, and “email” are included. As the name indicates, any scopes provided in this field will be included in addition to the defaults, rather than overwriting them. If one of the defaults is provided, it will only be included once.|
The current status of the Portal. The Portal will be processed as soon as it is created in the cluster.
|observedGeneration||int64||The observed generation of the Portal. When this matches the Portal’s metadata.generation, it indicates the status is up-to-date.|
|state||common.portal.gloo.solo.io.State||The current state of the portal.|
|reason||string||A human-readable string explaining the error, if any.|
|publishUrl||string||The published URL at which the portal can be accessed|
|publishedEnvironments||PortalStatus.EnvironmentInfo||repeated||The Environments and APIProducts that are currently considered to be part of this Portal.|
|name||string||The name of the Environment.|
|namespace||string||The namespace of the Environment.|
|apiProducts||common.portal.gloo.solo.io.ObjectRef||repeated||Environment APIProducts that are published.|