consul

Tree: 965c80e2eb

Author	SHA1	Message	Date
Freddy	965c80e2eb	Merge pull request #8099 from hashicorp/gateway-services-endpoint	5 years ago
freddygv	d97cff0966	Update telemetry for gateway-services endpoint	5 years ago
freddygv	cd927eed5e	Remove unused method and fixup docs ref	5 years ago
freddygv	0f97b7d63d	Fixup stray sid references	5 years ago
freddygv	b2c66359ab	Add docs	5 years ago
freddygv	19e3954603	Move compound service names to use ServiceName type	5 years ago
freddygv	e7b52d35d4	Create HTTP endpoint	5 years ago
freddygv	15c74d6943	Move GatewayServices out of Internal	5 years ago
Freddy	166a8b2a58	Only pass one hostname via EDS and prefer healthy ones (#8084 ) Co-authored-by: Matt Keeler <mkeeler@users.noreply.github.com> Currently when passing hostname clusters to Envoy, we set each service instance registered with Consul as an LbEndpoint for the cluster. However, Envoy can only handle one per cluster: [2020-06-04 18:32:34.094][1][warning][config] [source/common/config/grpc_subscription_impl.cc:87] gRPC config for type.googleapis.com/envoy.api.v2.Cluster rejected: Error adding/updating cluster(s) dc2.internal.ddd90499-9b47-91c5-4616-c0cbf0fc358a.consul: LOGICAL_DNS clusters must have a single locality_lb_endpoint and a single lb_endpoint, server.dc2.consul: LOGICAL_DNS clusters must have a single locality_lb_endpoint and a single lb_endpoint Envoy is currently handling this gracefully by only picking one of the endpoints. However, we should avoid passing multiple to avoid these warning logs. This PR: * Ensures we only pass one endpoint, which is tied to one service instance. * We prefer sending an endpoint which is marked as Healthy by Consul. * If no endpoints are healthy we emit a warning and skip the cluster. * If multiple unique hostnames are spread across service instances we emit a warning and let the user know which will be resolved.	5 years ago
John Cowen	54d69bbb8f	ui: Colocate pageobject components with their components (#8098 )	5 years ago
Kenia	0d88c4ef67	ui: Add health check icon to Ingress Upstreams and add Tooltips in additional areas (#8091 ) * Add Health Checks and update Tooltips in Ingress Upstreams * Update Tooltip in Proxy Info tab Upstreams * Add Tooltips to Proxy Info tab Exposed Paths * Add Health Checks with Tooltips to Service List page	5 years ago
John Cowen	8c6b6b4f17	ui: Ensure encoder.js polyfill is available (#8094 )	5 years ago
John Cowen	cdc249ec1a	ui: Exclude any component/pageobject.js files from being included (#7978 ) This excludes any /components/**/pageobject.js files from our production builds which means we can co-locate all of our component page objects (and selectors) along with the components themselves.	5 years ago
John Cowen	5817b8c4a8	ui: Upgrade consul-api-double to use intention response w/o old fields (#8089 )	5 years ago
Chris Piraino	6fa48c9512	Allow users to set hosts to the wildcard specifier when TLS is disabled (#8083 ) This allows easier demoing/testing of ingress gateways, while still preserving the validation we have for DNSSANs	5 years ago
Hans Hasselberg	b4b1a497e9	Adding 1.7.4 and 1.6.6	5 years ago
Hans Hasselberg	e62a43c6cf	Support envoy 1.14.2, 1.13.2, 1.12.4 (#8057 )	5 years ago
Chris Piraino	91ab89dd48	Move ingress param to a new endpoint (#8081 ) In discussion with team, it was pointed out that query parameters tend to be filter mechanism, and that semantically the "/v1/health/connect" endpoint should return "all healthy connect-enabled endpoints (e.g. could be side car proxies or native instances) for this service so I can connect with mTLS". That does not fit an ingress gateway, so we remove the query parameter and add a new endpoint "/v1/health/ingress" that semantically means "all the healthy ingress gateway instances that I can connect to to access this connect-enabled service without mTLS"	5 years ago
John Cowen	4bde23b9e9	Merge pull request #8080 from hashicorp/ui-staging ui: UI Release Merge (1.8-beta-3: ui-staging merge)	5 years ago
John Cowen	2838f7a2e9	ui: Reduce discovery-chain log errors (#8065 ) * ui: Reduce discovery-chain log spam Currently the only way that the UI can know whether connect is enabled or not is whether we get 500 errors from certain endpoints. One of these endpoints we already use, so aswell as recovering from a 500 error, we also remember that connect is disabled for the rest of the page 'session' (so until the page is refreshed), and make no further http requests to the endpoint for that specific datacenter. This means that log spam is reduced to only 1 log per page refresh/dc instead of 1 log per service navigation. Longer term we'll need some way to dynamically discover whether connect is enabled per datacenter without relying on something that will add error logs to consul.	5 years ago
Mike Wickett	8fab683389	Merge pull request #8076 from hashicorp/nq.basic-hero-tertiary-link-support [Website] Support tertiary-styled third links	5 years ago
John Cowen	db1ed14acf	ui: remove sort-control component (#8077 ) This was never actually used	5 years ago
Noel Quiles	1dfbd384da	Support tertiary-styled third links Get the tertiary links to wrap below buttons Adjust color/spacing of tertiary via override Remove overrides, implement custom link Extract arrow icon to file Increase top margin for third link Apply Brandon's fixes Co-authored-by: Brandon Romano <BrandonRRomano@gmail.com>	5 years ago
Kyle Havlovitz	8342542f7a	Merge pull request #8075 from hashicorp/expose-cli-testfix Fix a CLI test failure with namespaces in enterprise	5 years ago
Kyle Havlovitz	6fd3b25313	Fix a CLI test failure with namespaces in enterprise	5 years ago
Daniel Nephin	9132944e9a	Merge pull request #8071 from hashicorp/dnephin/update-vendor-2 Update google.golang.org/api and stretchr/testify	5 years ago
Chris Piraino	496e683360	Merge pull request #8064 from hashicorp/ingress/health-query-param Add API query parameter ?ingress to allow users to find ingress gateways associated to a service	5 years ago
Daniel Nephin	98d271bee9	Update google.golang.org/api and stretchr/testify To match the versions used in enterprise, should slightly reduce the chances of getting a merge conflict when using `go.mod`.	5 years ago
Chris Piraino	c1d329c5dd	Remove TODO note about ingress API, it is done!	5 years ago
Chris Piraino	5e0cd7ede5	Remove unnecessary defer from api.health_test.go We do not need to deregister services because every test gets its own instance of the client agent and the tmp directories are all deleted at the end.	5 years ago
Chris Piraino	ca41f80493	Set connect or ingress boolean after checking for query param	5 years ago
Daniel Nephin	08f1ed16b4	Merge pull request #7900 from hashicorp/dnephin/add-linter-staticcheck-2 intentions: fix a bug in Intention.SetHash	5 years ago
Daniel Nephin	62a1125c7b	Merge pull request #8037 from hashicorp/dnephin/add-linter-staticcheck-5 ci: Enabled SA2002 staticcheck check	5 years ago
Daniel Nephin	27ba56f3cd	Merge pull request #8067 from hashicorp/dnephin/update-vendor-1 Update protobuf and golang.org/x/... vendor	5 years ago
Hans Hasselberg	242994a016	acl: do not resolve local tokens from remote dcs (#8068 )	5 years ago
Kyle Havlovitz	0c8966220f	Merge pull request #8040 from hashicorp/ingress/expose-cli Ingress expose CLI command	5 years ago
Daniel Nephin	db74f09b6b	Update protobuf and golang.org/x/... vendor Partially extracted from #7547 Updates protobuf to the most recent in the 1.3.x series, and updates golang.org/x/sys to a7d97aace0b0 because of https://github.com/shirou/gopsutil/issues/853 prevents updating to a more recent version. This breaking change in x/sys also prevents us from getting a newer version of x/net. In the future, if gopsutil is not patched, we may want to run a fork version of gopsutil so that we can update both x/net and x/sys.	5 years ago
Kyle Havlovitz	e3a725c4e0	Always allow updating the exposed service and differentiate by namespace	5 years ago
Chris Piraino	4837069fe0	api: update api module with health.Ingress() method	5 years ago
Chris Piraino	3c037d9b96	Add ?ingress query parameter on /v1/health/connect Refactor boolean query parameter logic from ?passing value to re-use with ingress	5 years ago
Kenia	328874ad4f	ui: Reorder items in the Proxy Info tab (#8061 )	5 years ago
Preetha	25fe12053a	Merge pull request #8056 from hashicorp/docs-helm-survey Update banner.js to call out helm chart survey	5 years ago
Kenia	0ea5250cf6	ui: Reorder the tabs for Ingress/Terminating Gateway Service Detail page (#8060 )	5 years ago
John Cowen	aafbfa167c	ui: ConsulKind explanatory tooltip panels (#8048 ) * ui: Add tooltip panels to ConsulKind	5 years ago
Preetha	62b894a2d6	fix link	5 years ago
Kyle Havlovitz	edab5588d8	Add -host flag to expose command	5 years ago
Daniel Nephin	c66c533d73	Merge pull request #7964 from hashicorp/dnephin/remove-patch-slice-of-maps-forward-compat config: Use HookWeakDecodeFromSlice in place of PatchSliceOfMaps	5 years ago
Kyle Havlovitz	5958328552	Allow multiple listeners per service via expose command	5 years ago
Preetha	7983ab0fce	Update banner.js to call out helm chart survey	5 years ago
Daniel Nephin	75cbbe2702	config: add HookWeakDecodeFromSlice Currently opaque config blocks (config entries, and CA provider config) are modified by PatchSliceOfMaps, making it impossible for these opaque config sections to contain slices of maps. In order to fix this problem, any lazy-decoding of these blocks needs to support weak decoding of []map[string]interface{} to a struct type before PatchSliceOfMaps is replaces. This is necessary because these config blobs are persisted, and during an upgrade an older version of Consul could read one of the new configuration values, which would cause an error. To support the upgrade path, this commit first introduces the new hooks for weak decoding of []map[string]interface{} and uses them only in the lazy-decode paths. That way, in a future release, new style configuration will be supported by the older version of Consul. This decode hook has a number of advantages: 1. It no longer panics. It allows mapstructure to report the error 2. It no longer requires the user to declare which fields are slices of structs. It can deduce that information from the 'to' value. 3. It will make it possible to preserve opaque configuration, allowing for structured opaque config.	5 years ago

1 2 3 4 5 ...

11818 Commits (965c80e2ebe26fd654bcfcca2eede8327cb6263a) All Branches Search

11818 Commits (965c80e2ebe26fd654bcfcca2eede8327cb6263a)

All Branches